While currently only affecting local CI tests, there is a remaining node.js deprecation warning that could potentially become an error message later and halt workflows.
However, the component in question -- seanmiddleditch/gha-setup-vsdevenv -- seems stuck at v4 and the maintainer appears inactive. It also looks like it is more complex in that node.js native action case than just bumping a project reference (actual javascript changes appear needed). It's possible one of the other PRs there attempted something while proposing migration to a later core API version previously.
Possible alternatives could include migrating to a different action, manually patching the action, or contributing to the upstream project.
Current workaround being used locally just clones the repo manually and triggers installation in a way that absorbed the unwanted (and in this case unused) ::set-output action output. This is of course unideal.
While currently only affecting local CI tests, there is a remaining node.js deprecation warning that could potentially become an error message later and halt workflows.
However, the component in question -- seanmiddleditch/gha-setup-vsdevenv -- seems stuck at v4 and the maintainer appears inactive. It also looks like it is more complex in that node.js native action case than just bumping a project reference (actual javascript changes appear needed). It's possible one of the other PRs there attempted something while proposing migration to a later core API version previously.
References:
Possible alternatives could include migrating to a different action, manually patching the action, or contributing to the upstream project.
Current workaround being used locally just clones the repo manually and triggers installation in a way that absorbed the unwanted (and in this case unused)
::set-outputaction output. This is of course unideal.https://github.com/humbletim/setup-vulkan-sdk/blob/523828e49cd4afabce369c39c7ee6543a2b7a735/.github/workflows/ci.yml#L38-L51