fix(release): fail publish workflow on registry errors - #167
Open
victormartingil wants to merge 1 commit into
Open
fix(release): fail publish workflow on registry errors#167victormartingil wants to merge 1 commit into
victormartingil wants to merge 1 commit into
Conversation
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.
Summary\n- Remove hidden continue-on-error behavior from npm and VS Code Marketplace publish steps.\n- Add an explicit npm registry verification for the package version after publish.\n\n## Context\nRelease v2.35.0 created the GitHub Release and VSIX artifact, but npm still reports latest as 2.34.0. The npm publish log contains a registry 404 while the workflow job was marked successful because publish errors were ignored.\n\n## Verification\n- YAML-only workflow change; no runtime code changes.\n