Files
Javier Carrillo 128facbd37 chore(actions): update Node.js runtime from node20 to node24
Node.js 20 reaches EOL in April 2026 and GitHub Actions is deprecating
node20 runners. GitHub is skipping node22 and moving directly to node24.
All action.yml files updated to use node24 runtime.

Closes #87

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-03 12:19:55 -04:00
..
2024-04-24 14:03:13 +01:00

___

By default, all actions setup actual werf version for 1.2 alpha channel (more details about channels, werf release cycle and compatibility promise here). 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

- uses: werf/actions/install@v2
  with:
    channel: alpha

Withal, it is not necessary to work within release channels, and the user might specify certain werf version with version input.

- uses: werf/actions/install@v2
  with:
    version: v2.1.0

Inputs

channel:
  description: 'The one of the following channel: alpha, beta, ea, stable, rock-solid'
  default: 'stable'
  required: false
version:
  description: 'The certain version'
  required: false

Example

werf:
  name: werf 
  runs-on: ubuntu-latest
  steps:
  
    - name: Checkout code  
      uses: actions/checkout@v4

    - name: Install werf CLI  
      uses: werf/actions/install@v2
    
    # For deploy and distributed locks.
    - name: Create kube config
      run: |
        KUBECONFIG=$(mktemp -d)/config
        base64 -d <(printf "%s" $KUBE_CONFIG_BASE64_DATA) > $KUBECONFIG
        echo KUBECONFIG=$KUBECONFIG >> $GITHUB_ENV
      env:
        KUBE_CONFIG_BASE64_DATA: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
  
    - name: Run werf commands
      run: |
        source $(werf ci-env github --as-file)
        werf render
        werf converge
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        WERF_ENV: production