Repository navigation
Fix CLI-init package publishing conflicts - #16559
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
Check published versions through the local Verdaccio registry so pruning and publishing see the same packages. Add regression tests for scoped and unscoped packages. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues remain for the change aligning package-availability checks with the publishing registry.
No open issues 🎉
What changed in this PR
Fixes CLI-init duplicate-publish conflicts caused by checking package availability through a different registry than the one used for publishing after #16501.
Changes:
- Checks published versions through local Verdaccio, matching the publishing registry and its configured uplink.
- Adds Windows regression tests for published and unpublished scoped and unscoped packages.
- Documents the registry behavior and includes the tests in the root test command.
| File | Description |
|---|---|
package.json |
Adds the regression test file to the test command. |
.ado/tests/verdaccio-pruning.test.cjs |
Tests package pruning through the publishing registry using the actual CLI-init command. |
.ado/templates/verdaccio-start.yml |
Directs published-version checks to local Verdaccio. |
.ado/README.md |
Explains how matching registries prevents duplicate-publish conflicts. |
Review effort: Balanced
Nikolai Aristov (NikoAri)
approved these changes
Nov 2, 2026
Vladimir Morozov (vmoroz)
deleted the
PR/fix-verdaccio-publish-conflicts
branch
November 2, 2026 21:58
Vladimir Morozov (vmoroz)
added a commit
that referenced
this pull request
Nov 2, 2026
Vladimir Morozov (vmoroz)
added a commit
that referenced
this pull request
Nov 2, 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
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
After #16501, CLI-init checks for published packages through PackageFeedProxy,
while CI's Verdaccio uplink uses the authenticated Azure Artifacts feed. A version
missing from the proxy can already exist in that feed, causing an
E409conflictwhen the test tries to publish it again.
What
Registry consistency
publishing, so the lookup sees packages already present in its uplink.
Regression coverage
unscoped packages. Keep explicit test-file paths compatible with Node 24.
Screenshots
Not applicable; CI-only change.
Testing
Full CI passed before rebasing. On the rebased branch,
yarn test(Node 24.22.2),yarn lint:fix,yarn format, andyarn change --type prereleaseall passed;no change files 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