From 0d749fa2ee2631b7b066b188395ddacc865ab09a Mon Sep 17 00:00:00 2001 From: Alexey Igrychev Date: Thu, 28 May 2020 16:49:06 +0100 Subject: [PATCH] [readme] Switch to 1.1 alpha as default release channel --- README.md | 2 +- build-and-publish/README.md | 2 +- build/README.md | 2 +- cleanup/README.md | 2 +- converge/README.md | 2 +- deploy/README.md | 2 +- dismiss/README.md | 2 +- install/README.md | 2 +- publish/README.md | 2 +- run/README.md | 2 +- 10 files changed, 10 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index f233026..b1a5009 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,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 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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-and-publish/README.md b/build-and-publish/README.md index 348d1f8..da31d5c 100644 --- a/build-and-publish/README.md +++ b/build-and-publish/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 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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 796de31..0732dee 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 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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 32218b0..aeef69c 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 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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 4325784..1c11ffa 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 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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/deploy/README.md b/deploy/README.md index b35bc40..578a4c4 100644 --- a/deploy/README.md +++ b/deploy/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 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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 de06324..ea7a861 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 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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 95e33fe..c05bf64 100644 --- a/install/README.md +++ b/install/README.md @@ -3,7 +3,7 @@

___ -By default, all actions setup actual werf version for [1.1 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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/publish/README.md b/publish/README.md index 1b3eb90..4e1db01 100644 --- a/publish/README.md +++ b/publish/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 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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 ee47727..7b238c4 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 stable channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)). +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/flant/werf#backward-compatibility-promise)). Using `group` and `channel` inputs 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