Embed the MAJOR.MINOR version and remove the group input

2026-03-25 08:53:07 +03:00 · 2021-03-10 11:38:00 +00:00
parent da0172ca6e
commit 4dc23b175f
31 changed files with 87 additions and 174 deletions
--- a/README.md
+++ b/README.md
@@ -25,21 +25,20 @@ 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/converge@master
+- uses: werf/actions/converge@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/converge@master
+- uses: werf/actions/converge@v1.1
  with:
    version: v1.1.16
 ```
@@ -53,7 +52,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
 * Pass secret with `kube-config-base64-data` input:
 
  ```yaml
-  - uses: werf/actions/build-and-publish@master
+  - uses: werf/actions/build-and-publish@v1.1
    with:
      kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  ```
@@ -71,7 +70,7 @@ By default, action will use the token provided to your workflow.
 Any werf option can be defined with environment variables:

 ```yaml
- uses: werf/actions/build-and-publish@master
+- uses: werf/actions/build-and-publish@v1.1
  env:
    WERF_LOG_VERBOSE: "on"
    WERF_TAG_CUSTOM_TAG1: tag1
@@ -94,7 +93,7 @@ converge:
        fetch-depth: 0

    - name: Converge
-      uses: werf/actions/converge@master
+      uses: werf/actions/converge@v1.1
      with:
        env: production
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
@@ -114,7 +113,7 @@ build-and-publish:
        fetch-depth: 0

    - name: Build and Publish
-      uses: werf/actions/build-and-publish@master
+      uses: werf/actions/build-and-publish@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}

@@ -130,7 +129,7 @@ deploy:
        fetch-depth: 0

    - name: Deploy
-      uses: werf/actions/deploy@master
+      uses: werf/actions/deploy@v1.1
      with:
        env: production
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
@@ -148,7 +147,7 @@ dismiss:
      uses: actions/checkout@v2

    - name: Dismiss
-      uses: werf/actions/dismiss@master
+      uses: werf/actions/dismiss@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
        env: production
@@ -168,7 +167,7 @@ run:
        fetch-depth: 0

    - name: Run
-      uses: werf/actions/run@master
+      uses: werf/actions/run@v1.1
      with:
        image: backend
        args: rails server
@@ -192,7 +191,7 @@ cleanup:
      run: git fetch --prune --unshallow

    - name: Cleanup
-      uses: werf/actions/cleanup@master
+      uses: werf/actions/cleanup@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
 ```
@@ -206,10 +205,10 @@ werf:
  steps:
  
    - name: Checkout code  
-      uses: actions/checkout@master
+      uses: actions/checkout@v1.1

    - name: Install werf CLI  
-      uses: werf/actions/install@master
+      uses: werf/actions/install@v1.1
    
    # for deploy and distributed locks
    - name: Create kube config
--- a/action.yml
+++ b/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/build-and-publish/README.md
+++ b/build-and-publish/README.md
@@ -10,21 +10,20 @@ 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/build-and-publish@master
+- uses: werf/actions/build-and-publish@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/build-and-publish@master
+- uses: werf/actions/build-and-publish@v1.1
  with:
    version: v1.1.16
 ```
@@ -38,7 +37,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
 * Pass secret with `kube-config-base64-data` input:
 
  ```yaml
-  - uses: werf/actions/build-and-publish@master
+  - uses: werf/actions/build-and-publish@v1.1
    with:
      kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  ```
@@ -56,7 +55,7 @@ By default, action will use the token provided to your workflow.
 Any werf option can be defined with environment variables:

 ```yaml
- uses: werf/actions/build-and-publish@master
+- uses: werf/actions/build-and-publish@v1.1
  env:
    WERF_LOG_VERBOSE: "on"
    WERF_TAG_CUSTOM_TAG1: tag1
@@ -66,10 +65,6 @@ Any werf option can be defined with environment variables:
 ## Inputs

 ```yaml
-group:
-  description: 'The MAJOR.MINOR version'
-  default: '1.1'
-  required: false
 channel:
  description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
  default: 'alpha'
@@ -100,7 +95,7 @@ build-and-publish:
        fetch-depth: 0

    - name: Build and Publish  
-      uses: werf/actions/build-and-publish@master
+      uses: werf/actions/build-and-publish@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
 ```
--- a/build-and-publish/action.yml
+++ b/build-and-publish/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/build-and-publish/index.js
+++ b/build-and-publish/index.js
@@ -43793,9 +43793,9 @@ const tmp = __importStar(__webpack_require__(801));
 const dotenv = __importStar(__webpack_require__(972));
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD = 'https://werf.io/api/getChannelVersionURL';
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL';
+const MAJOR_MINOR_GROUP = '1.1';
 class Manager {
    constructor() {
-        this.group = core.getInput('group').trim();
        this.channel = core.getInput('channel').trim();
        this.version = core.getInput('version').trim();
        if (process.platform.toString() === 'win32') {
@@ -43877,7 +43877,7 @@ class Manager {
                else {
                    url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD;
                    query = {
-                        group: this.group,
+                        group: MAJOR_MINOR_GROUP,
                        channel: this.channel,
                        os: this.os,
                        arch: this.arch
--- a/build/README.md
+++ b/build/README.md
@@ -10,21 +10,20 @@ 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/build@master
+- uses: werf/actions/build@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/build@master
+- uses: werf/actions/build@v1.1
  with:
    version: v1.1.16
 ```
@@ -38,7 +37,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
 * Pass secret with `kube-config-base64-data` input:
 
  ```yaml
-  - uses: werf/actions/build@master
+  - uses: werf/actions/build@v1.1
    with:
      kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  ```
@@ -56,7 +55,7 @@ By default, action will use the token provided to your workflow.
 Any werf option can be defined with environment variables:

 ```yaml
- uses: werf/actions/build@master
+- uses: werf/actions/build@v1.1
  env:
    WERF_LOG_VERBOSE: "on"
    WERF_TAG_CUSTOM_TAG1: tag1
@@ -66,10 +65,6 @@ Any werf option can be defined with environment variables:
 ## Inputs

 ```yaml
-group:
-  description: 'The MAJOR.MINOR version'
-  default: '1.1'
-  required: false
 channel:
  description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
  default: 'alpha'
@@ -100,7 +95,7 @@ build:
        fetch-depth: 0

    - name: Build
-      uses: werf/actions/build@master
+      uses: werf/actions/build@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
 ```
--- a/build/action.yml
+++ b/build/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/build/index.js
+++ b/build/index.js
@@ -43793,9 +43793,9 @@ const tmp = __importStar(__webpack_require__(801));
 const dotenv = __importStar(__webpack_require__(972));
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD = 'https://werf.io/api/getChannelVersionURL';
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL';
+const MAJOR_MINOR_GROUP = '1.1';
 class Manager {
    constructor() {
-        this.group = core.getInput('group').trim();
        this.channel = core.getInput('channel').trim();
        this.version = core.getInput('version').trim();
        if (process.platform.toString() === 'win32') {
@@ -43877,7 +43877,7 @@ class Manager {
                else {
                    url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD;
                    query = {
-                        group: this.group,
+                        group: MAJOR_MINOR_GROUP,
                        channel: this.channel,
                        os: this.os,
                        arch: this.arch
--- a/cleanup/README.md
+++ b/cleanup/README.md
@@ -10,21 +10,20 @@ 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/cleanup@master
+- uses: werf/actions/cleanup@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/cleanup@master
+- uses: werf/actions/cleanup@v1.1
  with:
    version: v1.1.16
 ```
@@ -38,7 +37,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
 * Pass secret with `kube-config-base64-data` input:
 
  ```yaml
-  - uses: werf/actions/cleanup@master
+  - uses: werf/actions/cleanup@v1.1
    with:
      kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  ```
@@ -56,7 +55,7 @@ By default, action will use the token provided to your workflow.
 Any werf option can be defined with environment variables:

 ```yaml
- uses: werf/actions/cleanup@master
+- uses: werf/actions/cleanup@v1.1
  env:
    WERF_LOG_VERBOSE: "on"
 ```
@@ -64,10 +63,6 @@ Any werf option can be defined with environment variables:
 ## Inputs

 ```yaml
-group:
-  description: 'The MAJOR.MINOR version'
-  default: '1.1'
-  required: false
 channel:
  description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
  default: 'alpha'
@@ -99,7 +94,7 @@ cleanup:
      run: git fetch --prune --unshallow

    - name: Cleanup
-      uses: werf/actions/cleanup@master
+      uses: werf/actions/cleanup@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
 ```
--- a/cleanup/action.yml
+++ b/cleanup/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/cleanup/index.js
+++ b/cleanup/index.js
@@ -43793,9 +43793,9 @@ const tmp = __importStar(__webpack_require__(801));
 const dotenv = __importStar(__webpack_require__(972));
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD = 'https://werf.io/api/getChannelVersionURL';
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL';
+const MAJOR_MINOR_GROUP = '1.1';
 class Manager {
    constructor() {
-        this.group = core.getInput('group').trim();
        this.channel = core.getInput('channel').trim();
        this.version = core.getInput('version').trim();
        if (process.platform.toString() === 'win32') {
@@ -43877,7 +43877,7 @@ class Manager {
                else {
                    url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD;
                    query = {
-                        group: this.group,
+                        group: MAJOR_MINOR_GROUP,
                        channel: this.channel,
                        os: this.os,
                        arch: this.arch
--- a/converge/README.md
+++ b/converge/README.md
@@ -10,21 +10,20 @@ 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/converge@master
+- uses: werf/actions/converge@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/converge@master
+- uses: werf/actions/converge@v1.1
  with:
    version: v1.1.16
 ```
@@ -38,7 +37,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
 * Pass secret with `kube-config-base64-data` input:
 
  ```yaml
-  - uses: werf/actions/converge@master
+  - uses: werf/actions/converge@v1.1
    with:
      kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  ```
@@ -56,7 +55,7 @@ By default, action will use the token provided to your workflow.
 Any werf option can be defined with environment variables:

 ```yaml
- uses: werf/actions/converge@master
+- uses: werf/actions/converge@v1.1
  with:
    env: production
  env:
@@ -66,10 +65,6 @@ Any werf option can be defined with environment variables:
 ## Inputs

 ```yaml
-group:
-  description: 'The MAJOR.MINOR version'
-  default: '1.1'
-  required: false
 channel:
  description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
  default: 'alpha'
@@ -103,7 +98,7 @@ converge:
        fetch-depth: 0

    - name: Converge
-      uses: werf/actions/converge@master
+      uses: werf/actions/converge@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
        env: production
--- a/converge/action.yml
+++ b/converge/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/converge/index.js
+++ b/converge/index.js
@@ -43794,9 +43794,9 @@ const tmp = __importStar(__webpack_require__(801));
 const dotenv = __importStar(__webpack_require__(972));
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD = 'https://werf.io/api/getChannelVersionURL';
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL';
+const MAJOR_MINOR_GROUP = '1.1';
 class Manager {
    constructor() {
-        this.group = core.getInput('group').trim();
        this.channel = core.getInput('channel').trim();
        this.version = core.getInput('version').trim();
        if (process.platform.toString() === 'win32') {
@@ -43878,7 +43878,7 @@ class Manager {
                else {
                    url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD;
                    query = {
-                        group: this.group,
+                        group: MAJOR_MINOR_GROUP,
                        channel: this.channel,
                        os: this.os,
                        arch: this.arch
--- a/deploy/README.md
+++ b/deploy/README.md
@@ -10,21 +10,20 @@ 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/deploy@master
+- uses: werf/actions/deploy@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/deploy@master
+- uses: werf/actions/deploy@v1.1
  with:
    version: v1.1.16
 ```
@@ -38,7 +37,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
 * Pass secret with `kube-config-base64-data` input:
 
  ```yaml
-  - uses: werf/actions/deploy@master
+  - uses: werf/actions/deploy@v1.1
    with:
      kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  ```
@@ -56,7 +55,7 @@ By default, action will use the token provided to your workflow.
 Any werf option can be defined with environment variables:

 ```yaml
- uses: werf/actions/deploy@master
+- uses: werf/actions/deploy@v1.1
  with:
    env: production
  env:
@@ -66,10 +65,6 @@ Any werf option can be defined with environment variables:
 ## Inputs

 ```yaml
-group:
-  description: 'The MAJOR.MINOR version'
-  default: '1.1'
-  required: false
 channel:
  description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
  default: 'alpha'
@@ -103,7 +98,7 @@ deploy:
        fetch-depth: 0

    - name: Deploy
-      uses: werf/actions/deploy@master
+      uses: werf/actions/deploy@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
        env: production
--- a/deploy/action.yml
+++ b/deploy/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/deploy/index.js
+++ b/deploy/index.js
@@ -43758,9 +43758,9 @@ const tmp = __importStar(__webpack_require__(801));
 const dotenv = __importStar(__webpack_require__(972));
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD = 'https://werf.io/api/getChannelVersionURL';
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL';
+const MAJOR_MINOR_GROUP = '1.1';
 class Manager {
    constructor() {
-        this.group = core.getInput('group').trim();
        this.channel = core.getInput('channel').trim();
        this.version = core.getInput('version').trim();
        if (process.platform.toString() === 'win32') {
@@ -43842,7 +43842,7 @@ class Manager {
                else {
                    url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD;
                    query = {
-                        group: this.group,
+                        group: MAJOR_MINOR_GROUP,
                        channel: this.channel,
                        os: this.os,
                        arch: this.arch
--- a/dismiss/README.md
+++ b/dismiss/README.md
@@ -10,21 +10,20 @@ 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/converge@master
+- uses: werf/actions/converge@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/converge@master
+- uses: werf/actions/converge@v1.1
  with:
    version: v1.1.16
 ```
@@ -38,7 +37,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
 * Pass secret with `kube-config-base64-data` input:
 
  ```yaml
-  - uses: werf/actions/converge@master
+  - uses: werf/actions/converge@v1.1
    with:
      kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  ```
@@ -56,7 +55,7 @@ By default, action will use the token provided to your workflow.
 Any werf option can be defined with environment variables:

 ```yaml
- uses: werf/actions/converge@master
+- uses: werf/actions/converge@v1.1
  with:
    env: production
  env:
@@ -66,10 +65,6 @@ Any werf option can be defined with environment variables:
 ## Inputs

 ```yaml
-group:
-  description: 'The MAJOR.MINOR version'
-  default: '1.1'
-  required: false
 channel:
  description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
  default: 'alpha'
@@ -101,7 +96,7 @@ dismiss:
      uses: actions/checkout@v2

    - name: Dismiss
-      uses: werf/actions/dismiss@master
+      uses: werf/actions/dismiss@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
        env: production
--- a/dismiss/action.yml
+++ b/dismiss/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/dismiss/index.js
+++ b/dismiss/index.js
@@ -43794,9 +43794,9 @@ const tmp = __importStar(__webpack_require__(801));
 const dotenv = __importStar(__webpack_require__(972));
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD = 'https://werf.io/api/getChannelVersionURL';
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL';
+const MAJOR_MINOR_GROUP = '1.1';
 class Manager {
    constructor() {
-        this.group = core.getInput('group').trim();
        this.channel = core.getInput('channel').trim();
        this.version = core.getInput('version').trim();
        if (process.platform.toString() === 'win32') {
@@ -43878,7 +43878,7 @@ class Manager {
                else {
                    url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD;
                    query = {
-                        group: this.group,
+                        group: MAJOR_MINOR_GROUP,
                        channel: this.channel,
                        os: this.os,
                        arch: this.arch
--- a/install/README.md
+++ b/install/README.md
@@ -4,21 +4,20 @@
 ___
 
 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/install@master
+- uses: werf/actions/install@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/install@master
+- uses: werf/actions/install@v1.1
  with:
    version: v1.1.16
 ```
@@ -26,10 +25,6 @@ Withal, it is not necessary to work within release channels, and the user might
 ## Inputs

 ```yaml
-group:
-  description: 'The MAJOR.MINOR version'
-  default: '1.1'
-  required: false
 channel:
  description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
  default: 'alpha'
@@ -48,10 +43,10 @@ werf:
  steps:
  
    - name: Checkout code  
-      uses: actions/checkout@master
+      uses: actions/checkout@v1.1

    - name: Install werf CLI  
-      uses: werf/actions/install@master
+      uses: werf/actions/install@v1.1
    
    # for deploy and distributed locks
    - name: Create kube config
--- a/install/action.yml
+++ b/install/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/install/index.js
+++ b/install/index.js
@@ -17330,9 +17330,9 @@ const tmp = __importStar(__webpack_require__(801));
 const dotenv = __importStar(__webpack_require__(646));
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD = 'https://werf.io/api/getChannelVersionURL';
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL';
+const MAJOR_MINOR_GROUP = '1.1';
 class Manager {
    constructor() {
-        this.group = core.getInput('group').trim();
        this.channel = core.getInput('channel').trim();
        this.version = core.getInput('version').trim();
        if (process.platform.toString() === 'win32') {
@@ -17414,7 +17414,7 @@ class Manager {
                else {
                    url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD;
                    query = {
-                        group: this.group,
+                        group: MAJOR_MINOR_GROUP,
                        channel: this.channel,
                        os: this.os,
                        arch: this.arch
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
  "name": "werf-actions",
-  "version": "1.0.0",
+  "version": "1.1.0",
  "description": "",
  "main": "lib",
  "dependencies": {
--- a/publish/README.md
+++ b/publish/README.md
@@ -10,21 +10,20 @@ 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/publish@master
+- uses: werf/actions/publish@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/publish@master
+- uses: werf/actions/publish@v1.1
  with:
    version: v1.1.16
 ```
@@ -38,7 +37,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
 * Pass secret with `kube-config-base64-data` input:
 
  ```yaml
-  - uses: werf/actions/publish@master
+  - uses: werf/actions/publish@v1.1
    with:
      kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  ```
@@ -56,7 +55,7 @@ By default, action will use the token provided to your workflow.
 Any werf option can be defined with environment variables:

 ```yaml
- uses: werf/actions/publish@master
+- uses: werf/actions/publish@v1.1
  env:
    WERF_LOG_VERBOSE: "on"
    WERF_TAG_CUSTOM_TAG1: tag1
@@ -66,10 +65,6 @@ Any werf option can be defined with environment variables:
 ## Inputs

 ```yaml
-group:
-  description: 'The MAJOR.MINOR version'
-  default: '1.1'
-  required: false
 channel:
  description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
  default: 'alpha'
@@ -100,7 +95,7 @@ publish:
        fetch-depth: 0

    - name: Publish
-      uses: werf/actions/publish@master
+      uses: werf/actions/publish@v1.1
      with:
        kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
 ```
--- a/publish/action.yml
+++ b/publish/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/publish/index.js
+++ b/publish/index.js
@@ -43793,9 +43793,9 @@ const tmp = __importStar(__webpack_require__(801));
 const dotenv = __importStar(__webpack_require__(972));
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD = 'https://werf.io/api/getChannelVersionURL';
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL';
+const MAJOR_MINOR_GROUP = '1.1';
 class Manager {
    constructor() {
-        this.group = core.getInput('group').trim();
        this.channel = core.getInput('channel').trim();
        this.version = core.getInput('version').trim();
        if (process.platform.toString() === 'win32') {
@@ -43877,7 +43877,7 @@ class Manager {
                else {
                    url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD;
                    query = {
-                        group: this.group,
+                        group: MAJOR_MINOR_GROUP,
                        channel: this.channel,
                        os: this.os,
                        arch: this.arch
--- a/run/README.md
+++ b/run/README.md
@@ -10,21 +10,20 @@ 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)). 
-Using `group` and `channel` inputs the user can switch the release channel.
+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
  
 ```yaml
- uses: werf/actions/run@master
+- uses: werf/actions/run@v1.1
  with:
-    group: 1.1
    channel: alpha
 ```
  
 Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.

 ```yaml
- uses: werf/actions/run@master
+- uses: werf/actions/run@v1.1
  with:
    version: v1.1.16
 ```
@@ -38,7 +37,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
 * Pass secret with `kube-config-base64-data` input:
 
  ```yaml
-  - uses: werf/actions/run@master
+  - uses: werf/actions/run@v1.1
    with:
      kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  ```
@@ -56,7 +55,7 @@ By default, action will use the token provided to your workflow.
 Any werf option can be defined with environment variables:

 ```yaml
- uses: werf/actions/run@master
+- uses: werf/actions/run@v1.1
  env:
    WERF_LOG_VERBOSE: "on"
    WERF_TAG_CUSTOM_TAG1: tag1
@@ -67,10 +66,6 @@ Any werf option can be defined with environment variables:

 ```yaml
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
@@ -107,7 +102,7 @@ run:
        fetch-depth: 0

    - name: Run
-      uses: werf/actions/run@master
+      uses: werf/actions/run@v1.1
      with:
        image: backend
        args: rails server
--- a/run/action.yml
+++ b/run/action.yml
@@ -5,10 +5,6 @@ branding:
  color: blue
  icon: anchor
 inputs:
-  group:
-    description: 'The MAJOR.MINOR version'
-    default: '1.1'
-    required: false
  channel:
    description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
    default: 'alpha'
--- a/run/index.js
+++ b/run/index.js
@@ -43866,9 +43866,9 @@ const tmp = __importStar(__webpack_require__(801));
 const dotenv = __importStar(__webpack_require__(972));
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD = 'https://werf.io/api/getChannelVersionURL';
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL';
+const MAJOR_MINOR_GROUP = '1.1';
 class Manager {
    constructor() {
-        this.group = core.getInput('group').trim();
        this.channel = core.getInput('channel').trim();
        this.version = core.getInput('version').trim();
        if (process.platform.toString() === 'win32') {
@@ -43950,7 +43950,7 @@ class Manager {
                else {
                    url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD;
                    query = {
-                        group: this.group,
+                        group: MAJOR_MINOR_GROUP,
                        channel: this.channel,
                        os: this.os,
                        arch: this.arch
--- a/src/manager.ts
+++ b/src/manager.ts
@@ -13,9 +13,9 @@ import * as dotenv from 'dotenv'
 const WERF_API_GET_CHANNEL_VERSION_URL_METHOD =
  'https://werf.io/api/getChannelVersionURL'
 const WERF_API_GET_VERSION_URL_METHOD = 'https://werf.io/api/getVersionURL'
+const MAJOR_MINOR_GROUP = '1.1'

 export class Manager {
-  private readonly group: string
  private readonly channel: string
  private readonly version: string
  private readonly os: string
@@ -24,7 +24,6 @@ export class Manager {
  private binaryPath: string | undefined

  constructor() {
-    this.group = core.getInput('group').trim()
    this.channel = core.getInput('channel').trim()
    this.version = core.getInput('version').trim()

@@ -113,7 +112,7 @@ export class Manager {
      } else {
        url = WERF_API_GET_CHANNEL_VERSION_URL_METHOD
        query = {
-          group: this.group,
+          group: MAJOR_MINOR_GROUP,
          channel: this.channel,
          os: this.os,
          arch: this.arch