From 8037e10244fd01513131820057244af109f97537 Mon Sep 17 00:00:00 2001 From: Alexey Igrychev Date: Wed, 10 Mar 2021 14:33:13 +0000 Subject: [PATCH] [readme] Update default MAJOR.MINOR group and channel --- README.md | 2 +- build/README.md | 2 +- cleanup/README.md | 2 +- converge/README.md | 2 +- dismiss/README.md | 2 +- install/README.md | 2 +- run/README.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index bbccb7f..b0087c8 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ Each action combines all the necessary steps in itself and logic may be divided ### werf binary setup -By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). Using the `channel` input the user can switch the release channel. > This is recommended approach to be up-to-date and to use actual werf version without changing configurations diff --git a/build/README.md b/build/README.md index 42831c5..db77eca 100644 --- a/build/README.md +++ b/build/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). Using the `channel` input the user can switch the release channel. > This is recommended approach to be up-to-date and to use actual werf version without changing configurations diff --git a/cleanup/README.md b/cleanup/README.md index a5a67ef..216df01 100644 --- a/cleanup/README.md +++ b/cleanup/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). Using the `channel` input the user can switch the release channel. > This is recommended approach to be up-to-date and to use actual werf version without changing configurations diff --git a/converge/README.md b/converge/README.md index 6e7d178..2a3e14d 100644 --- a/converge/README.md +++ b/converge/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). Using the `channel` input the user can switch the release channel. > This is recommended approach to be up-to-date and to use actual werf version without changing configurations diff --git a/dismiss/README.md b/dismiss/README.md index 950e470..5d6b90e 100644 --- a/dismiss/README.md +++ b/dismiss/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). Using the `channel` input the user can switch the release channel. > This is recommended approach to be up-to-date and to use actual werf version without changing configurations diff --git a/install/README.md b/install/README.md index 501e23d..796fa31 100644 --- a/install/README.md +++ b/install/README.md @@ -3,7 +3,7 @@

___ -By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). Using the `channel` input the user can switch the release channel. > This is recommended approach to be up-to-date and to use actual werf version without changing configurations diff --git a/run/README.md b/run/README.md index 756bb08..efc515f 100644 --- a/run/README.md +++ b/run/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)). Using the `channel` input the user can switch the release channel. > This is recommended approach to be up-to-date and to use actual werf version without changing configurations