Hi team,
The v2.7.5 version of this action shipped a change bumping the required version of NodeJS to 20. This is a backwards-incompatible change, but was released as a patch version. This was unexpected and caused our workflows to start failing unexpectedly.
Our company has a contract with Hashicorp and we use GitHub Enterprise Server. GHES uses a different release cadence than GitHub Cloud, and our GHA runners are not compatible with Node20 yet. We have been impacted by several companies incorrectly marking these changes as patch versions, and they have graciously fixed the issue. We're currently working around the problem by pinning to version v2.7.4, however this is not ideal.
Can you please revert the v2.X version of the action to Node16 and release a new v3 version?
Hi team,
The v2.7.5 version of this action shipped a change bumping the required version of NodeJS to 20. This is a backwards-incompatible change, but was released as a patch version. This was unexpected and caused our workflows to start failing unexpectedly.
Our company has a contract with Hashicorp and we use GitHub Enterprise Server. GHES uses a different release cadence than GitHub Cloud, and our GHA runners are not compatible with Node20 yet. We have been impacted by several companies incorrectly marking these changes as patch versions, and they have graciously fixed the issue. We're currently working around the problem by pinning to version v2.7.4, however this is not ideal.
Can you please revert the v2.X version of the action to Node16 and release a new v3 version?