Publish core packages to ADO azure-sdk-for-js feed#11118
Open
timotheeguerin wants to merge 1 commit into
Open
Conversation
Core TypeSpec packages currently publish only to npmjs via ESRP. The CI consumption feed (azure-sdk-for-js) quarantines newly released packages for 7 days, so freshly released packages are not installable for a week. Publish the .tgz artifacts directly to the ADO feed (bypassing the quarantine) before the npm/ESRP publish, matching the existing emitter pipeline pattern. Already-published versions are skipped; genuine failures fail the pipeline.
Contributor
|
No changes needing a change description found. |
|
You can try these changes here
|
timotheeguerin
requested review from
bterlson,
catalinaperalta,
iscai-msft,
markcowl and
witemple-msft
as code owners
markcowl
approved these changes
Jul 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
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.
Problem
CI (and this repo's emitter pipelines) install npm packages from the ADO feed
azure-sdk-for-js(https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-js/npm/registry/), which quarantines newly released npmjs packages for 7 days. Core@typespec/*packages currently publish only to npmjs via ESRP, so freshly released versions are not installable from the feed for a week.Change
Publish the built
.tgzartifacts directly to the ADO feed (which bypasses the upstream quarantine) before the existing npm/ESRP publish, applying the dual-publish pattern already used by this repo's emitter pipeline (eng/emitters/.../emitter-stages.yml) and every Azure SDK repo (archetype-typespec-emitter.yml).eng/tsp-core/pipelines/templates/release/ado-feed-release.yml— mirrorsesrp-release.yml; reusescreate-authenticated-npmrc.yml(registry = the feed) + anpm publish --access public --tag <tag>loop.EPUBLISHCONFLICT/409), matching today's npm behavior of not republishing.SkipPublishingfor dry runs.eng/tsp-core/pipelines/jobs/publish-npm.yml— runs the ADO-feed step before ESRP, for both stable/latestand next/next(no change topublish.yml).Notes / follow-ups
@typespec/*publish rights on theazure-sdk-for-jsfeed (emitters already publish@azure-tools/*there). Please confirm with EngSys.releaseJobrestrictsnpmAuthenticate/npm publish, fallback is to move the ADO publish to a separate normal job that the ESRP deployment jobdependsOn.