Skip to content

[release/v7.7.0-preview.1] Remove mariner2.0 from PMC mapping#27353

Merged
jshigetomi merged 1 commit intoPowerShell:release/v7.7.0-preview.1from
jshigetomi:backport/release/v7.7.0-preview.1/27068-0458f16cc
Apr 24, 2026
Merged

[release/v7.7.0-preview.1] Remove mariner2.0 from PMC mapping#27353
jshigetomi merged 1 commit intoPowerShell:release/v7.7.0-preview.1from
jshigetomi:backport/release/v7.7.0-preview.1/27068-0458f16cc

Conversation

@jshigetomi
Copy link
Copy Markdown
Collaborator

Backport of #27068 to release/v7.7.0-preview.1

Triggered by @jshigetomi on behalf of @anamnavi

Original CL Label: CL-BuildPackaging

/cc @PowerShell/powershell-maintainers

Impact

REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.

Tooling Impact

  • Required tooling change
  • Optional tooling change (include reasoning)

Required tooling change. Updates the PMC (packages.microsoft.com) mapping configuration used by the release publish pipeline. PowerShell 7.6+ does not support Mariner 2.0; without this change, the v7.7.0-preview.1 release pipeline would attempt to publish packages to Mariner 2.0 repos that should no longer receive them. Users on Mariner-family distros should consume PowerShell from the AzureLinux 3 PMC feed instead.

Customer Impact

  • Customer reported
  • Found internally

Regression

REQUIRED: Check exactly one box.

  • Yes
  • No

This is not a regression.

Testing

Verified by:

  1. Cherry-picking the merge commit cleanly onto release/v7.7.0-preview.1 with no conflicts.
  2. Functional verification will occur during the actual v7.7.0-preview.1 PMC release — the publish pipeline will no longer attempt to push to Mariner 2.0 repositories.

No new tests required: change is config-only (PMC mapping table).

Risk

REQUIRED: Check exactly one box.

  • High
  • Medium
  • Low

Low risk: change is isolated to the PMC mapping.json file (PowerShell package distribution config). It removes Mariner 2.0 entries because PowerShell 7.6+ is not supported on Mariner 2.0 — users on that distro should use AzureLinux 3 packages instead. No code changes, no runtime behavior change for end users; only affects which Mariner repository receives published packages during PMC publishing. Required for v7.7.0-preview.1 to keep its PMC mapping consistent with the supported-distro matrix. Note: original PR has only Backport-7.6.x-Consider (no 7.7.x label) — proceeding at user request.

Co-authored-by: Justin Chung <124807742+jshigetomi@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 24, 2026 17:53
@jshigetomi jshigetomi added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Apr 24, 2026
@jshigetomi jshigetomi requested a review from a team as a code owner April 24, 2026 17:53
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Backports the PMC (packages.microsoft.com) publish mapping change to the release/v7.7.0-preview.1 branch so the release pipeline no longer targets Mariner 2.0 repositories (which are not supported for PowerShell 7.6+).

Changes:

  • Removed all cbl-mariner-2.0-* entries (stable + preview, x86_64 + aarch64) from the PMC mapping.json.

@jshigetomi jshigetomi merged commit ead21d9 into PowerShell:release/v7.7.0-preview.1 Apr 24, 2026
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

3 participants