ci: reset exit codes in idempotent npm/vsce publish checks#7897
Merged
Conversation
The npm-check pwsh step and the vs_marketplace AzureCLI inlineScript correctly detected already-published versions, but the trailing native command (npm view E404 / vsce publish 'already exists') left \0 non-zero, causing the whole step to fail on idempotent re-runs. Capture and reset the leftover exit code and end both scripts with 'exit 0'; genuine failures still throw and surface as non-zero. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Code Coverage OverviewLanguages: C# C# / code-coverage/dotnetThe overall coverage in the branch is 72%. Coverage data for the branch is not yet available. Show a code coverage summary of the most covered files.
Updated |
adrian05-ms
approved these changes
Jul 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
2 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.
Follow-up to #7895. The idempotent npm and vs_marketplace publish checks detected already-published versions correctly, but the trailing native command left
$LASTEXITCODEnon-zero, failing the step on re-runs (build 225636 failed at npm-check and vs_marketplace for exactly this reason).Fix: capture and reset the leftover exit code and end both scripts with
exit 0. Genuine failures stillthrowand surface as non-zero exits.No source/behavioral changes — pipeline YAML only; validated with
yaml.safe_load.