build(vscode-extension): disable make_latest on github release publication#69139
Open
alan-agius4 wants to merge 1 commit into
Open
build(vscode-extension): disable make_latest on github release publication#69139alan-agius4 wants to merge 1 commit into
alan-agius4 wants to merge 1 commit into
Conversation
…ation Previously, when releasing the VS Code extension, the draft release was created with make_latest: 'false', but the PATCH request that published the draft release omitted this option. As a result, GitHub automatically designated the published release as the 'latest' release. This change explicitly passes make_latest: 'false' during the publish request to prevent it from automatically becoming the latest release.
2b02d0a to
d5d27fd
Compare
crisbeto
approved these changes
Jun 4, 2026
atscott
approved these changes
Jun 4, 2026
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
3 participants
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.
Previously, when releasing the VS Code extension, the draft release was created with make_latest: 'false', but the PATCH request that published the draft release omitted this option. As a result, GitHub automatically designated the published release as the 'latest' release.
This change explicitly passes make_latest: 'false' during the publish request to prevent it from automatically becoming the latest release.