build(wrapper): add the internal-feed release pipeline and install guide - #3753
Open
Joywambui-maina wants to merge 6 commits into
Open
build(wrapper): add the internal-feed release pipeline and install guide#3753Joywambui-maina wants to merge 6 commits into
Joywambui-maina wants to merge 6 commits into
Conversation
Builds and packs the wrapper modules from committed sources, verifies packages were actually produced before signing, ESRP-signs, and publishes to the project-scoped MSGraph_PowerShell_V3_Build feed. Mirrors sdk-release.yml - same 1ES template, security templates and publish task - with no AutoRest or Node bootstrap, manual trigger only, and Publish defaulting to false so the first runs produce a drop artifact without pushing packages. The guide covers feed registration and Install-Module -AllowPrerelease for testers.
Member
|
Waiting for #3756 to be updated per my review comment and merged. Once that lands, this pipeline should be tested end-to-end from this branch to verify that packages are published to the feed successfully. |
Joywambui-maina
added a commit
that referenced
this pull request
Aug 28, 2026
The guide rides #3753 to powershell-v3, where the wrapper modules live; main only carries the pipeline definition.
Joywambui-maina
added a commit
that referenced
this pull request
Aug 28, 2026
…ide (main) (#3756) * build(wrapper): add the internal-feed release pipeline and install guide Builds and packs the wrapper modules from committed sources, verifies packages were actually produced before signing, ESRP-signs, and publishes to the project-scoped MSGraph_PowerShell_V3_Build feed. Mirrors sdk-release.yml - same 1ES template, security templates and publish task - with no AutoRest or Node bootstrap, manual trigger only, and Publish defaulting to false so the first runs produce a drop artifact without pushing packages. The guide covers feed registration and Install-Module -AllowPrerelease for testers. * docs(wrapper): keep the install guide off main The guide rides #3753 to powershell-v3, where the wrapper modules live; main only carries the pipeline definition.
The pipeline reused install-tools.yml wholesale, which is the AutoRest toolchain - Node, the private npm feed, AutoRest, Rush and a full rush rebuild - none of which the wrapper build touches, and it installs .NET 8/6 while the generator targets net10.0. The build step then failed because Build-WrapperModule.ps1 refuses to run without the kiota CLI on PATH even under -SkipKiota. Installs the .NET 10 SDK, feed auth, and kiota explicitly.
…solation api.nuget.org is not reliably reachable from the 1ES pool, so the kiota tool install failed loading the service index - and the module restore would have failed the same way one step later. Writes a pipeline-local nuget.config that puts the MSGraph_PowerShell_V3_Build feed (whose upstream proxies nuget.org) first with nuget.org as fallback, used by every restore on the run. NuGetAuthenticate supplies the credentials; the kiota step also retries.
dotnet tool install probes the service index of every configured source and fails hard if any is unreachable, so keeping nuget.org as a fallback defeated the routing entirely. The pipeline config now lists only the internal feed, whose upstream proxies nuget.org, and the install ignores failed sources.
Per review: the pipeline now generates the kiota client from the committed OpenAPI docs and the wrappers on top, then compiles - the whole process is built and tested end to end on every run, and a run can never fail on committed clients lagging the docs. Clients remain committed to the repo for reviewable diffs and clean local checkouts.
This was referenced Aug 28, 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
3 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.
Changes proposed in this pull request
.azure-pipelines/wrapper-release.yml: builds and packs the wrapper modules from committed sources, verifies packages were actually produced before signing, ESRP-signs, and publishes to the project-scopedGraph Developer Experiences/MSGraph_PowerShell_V3_Buildfeed. Mirrorssdk-release.yml- same 1ES template, security templates (pre-checks, guardian-analyzer, codesign-nuget, post-checks) and1ES.PublishNuget@1task.Publishdefaults tofalse, so the first runs produce a signeddropartifact without pushing packages to the feed.Build-WrapperModule.ps1 -ModuleVersion/-Prerelease(3.0.0-alpha<build id>); nothing editsModuleMetadata.json, which belongs to the v2 release train.docs/install-wrapper-modules-from-feed.md: feed registration andInstall-Module -AllowPrereleaseinstructions for testers.Note: a run can only succeed once the wrapper stack through #3740 has merged (the script's
-ModuleVersion/-Prereleasesurface and the package identity fixes land there). The pipeline is inert until then - manual trigger, no CI hooks.Other links