Skip to content

Add stage to publish Microsoft.PowerShell.PSResourceGet to ADO feed - #2058

Merged
Anam Navied (anamnavi) merged 2 commits into
PowerShell:masterfrom
anamnavi:pipeline-publish-artifactfeed
Sep 21, 2026
Merged

Anam Navied (anamnavi) merged 2 commits into
PowerShell:masterfrom
anamnavi:pipeline-publish-artifactfeed

Conversation

@anamnavi

@anamnavi Anam Navied (anamnavi) commented Sep 21, 2026

Copy link
Copy Markdown
Member

PR Summary

Add stage to publish Microsoft.PowerShell.PSResourceGet to internal ADO feed in addition to PSGallery.

PR Context

PR Checklist

@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

Choose a reason for hiding this comment

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

Copilot review overview

🟡 Changes recommended

Feed authentication is misconfigured, and the new stage can publish PR artifacts without a release gate.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 2 High severity · 1 Low severity

Open (3)
What changed in this PR

Adds ADO CFS-feed publishing to the official PSResourceGet release pipeline.

Changes:

  • Adds a CFS feed publication stage.
  • Adds a parameter to optionally skip PSGallery publishing.
  • Adds feed-related pipeline configuration.
File Description
.pipelines/​PSResourceGet-Official.yml Adds CFS publishing and conditional PSGallery release logic.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .pipelines/PSResourceGet-Official.yml
Comment thread .pipelines/PSResourceGet-Official.yml
Comment thread .pipelines/PSResourceGet-Official.yml
Comment thread .pipelines/PSResourceGet-Official.yml Outdated
Co-authored-by: Aditya Patwardhan <adityap@microsoft.com>
@anamnavi
Anam Navied (anamnavi) merged commit 519eb7a into PowerShell:master Sep 21, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants