ci(extension): Node 24-ready actions + idempotent release attach#2
Merged
Conversation
- actions/checkout@v4 -> v6, actions/setup-node@v4 -> v6, node 20 -> 22. GitHub force-deprecates Node 20 actions on June 16 2026; this matches release.yml. - "Attach .vsix to a GitHub Release" now upserts (gh release upload --clobber when the release already exists) so a re-run — e.g. after configuring a publish PAT — no longer fails on the already-created release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two fixes to
extension-release.yml, both surfaced while cuttingext-v0.3.0:actions/checkout@v4+actions/setup-node@v4run on Node 20, which GitHub force-deprecates June 16, 2026. Bumped to@v6(and node 20 → 22) to matchrelease.yml, which already uses v6.gh release createstep failed on theext-v0.3.0re-run because the release already existed. It now upserts (gh release upload --clobberwhen the release exists), so re-running a release tag — e.g. after adding a publish PAT — no longer fails on the already-created release.No engine or extension code touched.
🤖 Generated with Claude Code