Repository navigation
[0.81] Fix CLI-init package publishing conflicts - #16560
Merged
Vladimir Morozov (vmoroz) merged 1 commit intoNov 2, 2026
Merged
Vladimir Morozov (vmoroz) merged 1 commit into
Vladimir Morozov (vmoroz) merged 1 commit into
Conversation
Backport of microsoft#16559. (cherry picked from commit 79774fa) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are recorded for the backport aligning version checks with the local Verdaccio publishing registry.
No open issues 🎉
What changed in this PR
Backports the CLI-init publishing fix to 0.81-stable, aligning package-version checks with the local Verdaccio publish registry to avoid duplicate-publish conflicts.
Changes:
- Check existing versions through Verdaccio rather than the default package proxy.
- Add Windows regression tests for scoped and unscoped packages while preserving release-detection tests.
- Document why lookup and publishing must use the same registry.
| File | Description |
|---|---|
package.json |
Adds pruning tests to the existing test command. |
.ado/tests/verdaccio-pruning.test.cjs |
Verifies published versions are removed and unpublished versions retained using the publish registry. |
.ado/templates/verdaccio-start.yml |
Directs pre-publish version checks to local Verdaccio. |
.ado/README.md |
Explains registry consistency and duplicate-publish prevention. |
Review effort: Balanced
Vladimir Morozov (vmoroz)
enabled auto-merge (squash)
November 2, 2026 22:49
Nikolai Aristov (NikoAri)
approved these changes
Nov 2, 2026
Vladimir Morozov (vmoroz)
merged commit Nov 2, 2026
fbf34ed
into
microsoft:0.81-stable
36 checks passed
Vladimir Morozov (vmoroz)
deleted the
PR/fix-verdaccio-publish-conflicts-0.81
branch
November 2, 2026 23:36
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
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.
Description
Type of Change
Why
Backport of #16559 to
0.81-stable. Package lookup uses PackageFeedProxy, whileCI's Verdaccio uplink uses the authenticated Azure Artifacts feed. Versions missing
from the proxy can already exist in that feed, causing duplicate-publish errors.
What
Registry consistency
publishing, so the lookup sees packages already present in the uplink.
Regression coverage
test command, preserving its release-detection tests.
Screenshots
Not applicable; CI-only change.
Testing
yarn testpassed on Node 24.22.2;yarn lint:fixandyarn formatpassed.yarn change --type prerelease --branch upstream/0.81-stablepassed; no changefiles were needed.
Changelog
Should this change be included in the release notes: no
Fix duplicate package publishing in CLI-init validation.
Microsoft Reviewers: Open in CodeFlow