Skip to content

Cherry-pick #18033 + #18034 (container-publishing fixes) to 3.0-dev - #18244

Open
jslobodzian wants to merge 2 commits into
3.0-devfrom
jslobodzian/cherry-pick-18033-18034-to-3.0-dev
Open

Cherry-pick #18033 + #18034 (container-publishing fixes) to 3.0-dev#18244
jslobodzian wants to merge 2 commits into
3.0-devfrom
jslobodzian/cherry-pick-18033-18034-to-3.0-dev

Conversation

@jslobodzian

Copy link
Copy Markdown
Collaborator

Manual cherry-pick of two PRs that landed on fasttrack/3.0 on 7/16 but never auto-forward-picked into 3.0-dev:

Both PRs are follow-up fixes on top of #18026 (which merged directly to 3.0-dev). They touch only .pipelines/containerSourceData/scripts/PublishContainers.sh.

Verified with git diff origin/fasttrack/3.0..HEAD -- .pipelines/containerSourceData/scripts/PublishContainers.sh → empty (file state matches fasttrack/3.0 exactly).

Cherry-picks applied cleanly with git cherry-pick -x, no conflicts. Each original PR is preserved as its own commit — please do not squash-merge.

@jslobodzian
jslobodzian requested a review from a team as a code owner July 28, 2026 20:39
@microsoft-github-policy-service microsoft-github-policy-service Bot added the 3.0-dev PRs Destined for AzureLinux 3.0 label Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants