build(wrapper): add the internal-feed release pipeline and install guide (main) - #3756
Merged
Merged
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.
The guide rides #3753 to powershell-v3, where the wrapper modules live; main only carries the pipeline definition.
Peter Ombwa (peombwa)
approved these changes
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
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.
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.Same content as #3753 (which targets
powershell-v3); this twin lands it onmainso the AzDo pipeline definition can register against the default branch. Onmainthe pipeline is inert - the wrapper tooling it invokes lives on thepowershell-v3line, so runs should select that branch until v3 ships.Other links