Context
Part of #4115 — updating GitHub Actions that use deprecated Node.js 20.
HaaLeo/publish-vscode-extension@v2 still uses Node 20 and there is no newer release with Node 24 support. This action is used in publish.yaml for publishing to both the VS Marketplace and Open VSX Registry.
Action needed
Deadline
GitHub will force Node.js 24 starting June 16, 2026. Node.js 20 will be removed from runners on September 16, 2026.
Alternatives if upstream doesn't update in time
- Replace with direct
vsce publish and ovsx publish CLI commands.
- Set
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true env var as a temporary workaround.
UPDATE (6/3/26):
The way forward I think is to produce a common GH action owned by posit to publish to the vsix registries.
posit-dev/posit-gh-actions#2
The actual code needed to implement the publish is really minimal - there's no need for anything beyond direct command line invocations, the action itself can just be tens of lines.
Context
Part of #4115 — updating GitHub Actions that use deprecated Node.js 20.
HaaLeo/publish-vscode-extension@v2still uses Node 20 and there is no newer release with Node 24 support. This action is used inpublish.yamlfor publishing to both the VS Marketplace and Open VSX Registry.Action needed
.github/workflows/publish.yaml(lines 41 and 69).Deadline
GitHub will force Node.js 24 starting June 16, 2026. Node.js 20 will be removed from runners on September 16, 2026.
Alternatives if upstream doesn't update in time
vsce publishandovsx publishCLI commands.FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=trueenv var as a temporary workaround.UPDATE (6/3/26):
The way forward I think is to produce a common GH action owned by posit to publish to the vsix registries.
posit-dev/posit-gh-actions#2
The actual code needed to implement the publish is really minimal - there's no need for anything beyond direct command line invocations, the action itself can just be tens of lines.