🐛 [bug]: using v1 gives node16 deprecation warnings

[joernott]

🐛 What happened?

We start seeing deprecation warnings aboud node16 when using raven-actions/actionlint@v1:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

🔬 How to reproduce?

Call actionlint action

🏗️ Code Sample / Log

[...]
  actionlint:
    needs: ['init', 'begin_report_phase']
    if: ${{ always() && needs.init.outputs.actionlint_skip != 'true' }}
    runs-on: ${{ fromJSON(inputs.runs_on) }}
    steps:
      - name: Install npm on private runner
        if: ${{ inputs.runs_on != '"ubuntu-latest"'}}
        run: |
          NPM=$(type -p 'npm'||true)
          if [ -z "${NPM}" ]; then
            echo -e "\033[0;35m###  Installing npm ###\033[0m"
            sudo DEBIAN_FRONTEND=noninteractive apt-get -qq update
            sudo apt-get -qq install npm
          fi

      - name: Checkout
        id: checkout
        uses: actions/checkout@v4

      - name: Run actionlint
        id: actionlint
        uses: raven-actions/actionlint@v1

🌌 Environment (actionlint action)

1.0.3

🌌 Environment (actionlint)

1.6.26-Linux-X64

🌌 Environment (GitHub Runner OS)

Linux

📷 Screenshots

No response

📈 Expected behavior

actions/cache is upgraded to v4 to remove the warning

📎 Additional context

No response

📜 Code of Conduct

• I agree to follow this project's Code of Conduct.

[mvanduijker]

It should have been fixed with this #20
We have to wait for a new release.

[DariuszPorowski]

Will review, bump deps, test and release new one around end of 1st week of March.

[mvanduijker]

any way I can help to get this released?

[pakosak]

any update on the release @DariuszPorowski ?

[DariuszPorowski]

@mvanduijker @pakosak currently this PR is a blocker: #22
After will solve it, then breaking change (v2 release) will happen with switch to node20

[kxc171]

@DariuszPorowski - Any plans to still cutover a v2 tag for this yet (or update the existing v1 tag)? This would be really nice to address since at this point GH has started forcing Node20 as on June 3rd. https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

[DariuszPorowski]

@kxc171 done :) v2 released :)

[rindeal]

@DariuszPorowski Great, but this time around could you use tags only for specific versions like 2.0.0 and branches for v2, v3, ...? This will make hotfixes like node16 -> node20 much easier.

[DariuszPorowski]

@rindeal, thanks for the suggestion. I started thinking to skip any major tags at all and do only semver, going further looking for GitHub feature like github/roadmap#592