1.29.0-1 causing issue during setup about buf-setup-action

[emcfarlane]

I believe the wrong version is being cached but should hopefully be fixed. I'll re-open until we can confirm.

[Radisovik]

So going to v1.29.0-1 should make things happy? maybe my enterprise github is caching something...

Error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ''using: node20' is not supported, use 'docker', 'node12' or 'node16' instead.')
at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs)
at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Error: Fail to load bufbuild/buf-setup-action/v1.29.0-1/action.yml

[sicoyle]

I can confirm this is indeed an issue rn so thanks for looking into this! 😅

[emcfarlane]

Sorry for the issue! Lastest should be at 1.29.0 and we will add better testing for future release. Thanks for reporting. Please let me know if you have any issues.

[passichenko]

I'm still seeing this error. Our setup is:

      - uses: bufbuild/buf-setup-action@v1
        with:
          buf_user: ${{ secrets.BUF_USER }}
          buf_api_token: ${{ secrets.BUF_API_TOKEN }}
          github_token: ${{ secrets.CI_PERSONAL_ACCESS_TOKEN }}

I'm not very familiar with github action versioning, but don't you need to cut a release? Or should we use some other tag?

[passichenko]

changing it to bufbuild/[email protected] worked

[passichenko]

maybe it's because this run failed and it didn't push to v1 branch?
https://github.com/bufbuild/buf-setup-action/actions/runs/7995772216

[emcfarlane]

Thank you @passichenko ! That is exactly it, pushed up and checked, v1 resolves.

[emcfarlane]

@Radisovik thanks for reporting. This looks like a different issue related to the recent node version change. Could you use 1.29.0 for now to ensure you use the node16 runtime and raise an issue with more details?