Skip to content

Add ability to consume PowerShell modules from internal feed - #28326

Merged
Aditya Patwardhan (adityapatwardhan) merged 1 commit into
masterfrom
consumeInternalModules
Nov 5, 2026
Merged

Aditya Patwardhan (adityapatwardhan) merged 1 commit into
masterfrom
consumeInternalModules

Conversation

@adityapatwardhan

Copy link
Copy Markdown
Member

PR Summary

Add the ability to consume PowerShell modules from an internal feed for official builds.

PR Context

PR Checklist

Copilot AI balanced review requested due to automatic review settings November 4, 2026 05:22
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Both vPack build paths omit the secret feed credential mapping when UseEarlyAccessModules=true and IsEarlyAccess=false, preventing module restores from using the new feed token.

2 open issues
What changed in this PR

Adds opt-in internal module feeds to PowerShell’s build infrastructure, independently of early-access .NET feeds.

Changes:

  • Adds UseEarlyAccessModules parameters to official and nonofficial pipelines.
  • Updates NuGet configuration and authentication to include the internal module feed.
  • Adds configuration tests and documents pipeline and local restore usage.
File Description
test/​infrastructure/​NugetConfig.Tests.ps1 Tests feed selection and authentication behavior.
docs/​building/​internals.md Documents internal module feeds and restore requirements.
build.psm1 Adds independent internal module source selection.
.pipelines/​templates/​insert-nuget-config-azfeed.yml Configures and authenticates enabled internal feeds.
.pipelines/​PowerShell-vPack-Official.yml Exposes the module-feed option for official vPack builds.
.pipelines/​PowerShell-Release-Official.yml Exposes the option for official releases.
.pipelines/​PowerShell-Packages-Official.yml Exposes the option for official packaging.
.pipelines/​PowerShell-Coordinated_Packages-Official.yml Exposes the option for official coordinated packaging.
.pipelines/​NonOfficial/​PowerShell-vPack-NonOfficial.yml Exposes the option for nonofficial vPack builds.
.pipelines/​NonOfficial/​PowerShell-Release-NonOfficial.yml Exposes the option for nonofficial releases.
.pipelines/​NonOfficial/​PowerShell-Packages-NonOfficial.yml Exposes the option for nonofficial packaging.
.pipelines/​NonOfficial/​PowerShell-Coordinated_Packages-NonOfficial.yml Exposes the option for nonofficial coordinated packaging.
.pipelines/​MSIXBundle-vPack-Official.yml Exposes the option for MSIX bundle vPack builds.
.pipelines/​apiscan-gen-notice.yml Exposes the option for API scanning and notice generation.

Review effort: Balanced

Comment on lines +53 to +54
- name: UseEarlyAccessModules
value: ${{ parameters.UseEarlyAccessModules }}
Comment on lines +60 to +61
- name: UseEarlyAccessModules
value: ${{ parameters.UseEarlyAccessModules }}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backport-7.6.x-Done Backport-7.7.x-Migrated CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants