[release/9.0-staging] Update Debian 12 to Debian 13 helix references#122326
Closed
Copilot wants to merge 2 commits intorelease/9.0-stagingfrom
Closed
[release/9.0-staging] Update Debian 12 to Debian 13 helix references#122326Copilot wants to merge 2 commits intorelease/9.0-stagingfrom
Copilot wants to merge 2 commits intorelease/9.0-stagingfrom
Conversation
Co-authored-by: richlander <2608468+richlander@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update Debian 12 helix references to Debian 13
Update Debian 12 to Debian 13 helix references
Dec 9, 2025
Contributor
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
Member
|
/ba-g "Unrelated failures" |
Member
|
@jkoritzinsky @sbomer This looks ready for approval. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates helix test queue configurations from Debian 12 to Debian 13 across CoreCLR and libraries pipeline templates. This is an infrastructure update with no direct customer impact, aligning the test queues with the current Debian release.
Key changes:
- Updated helix queue names from
Debian.12.*toDebian.13.* - Updated container image tags from
debian-12-helix-*todebian-13-helix-*
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
eng/pipelines/libraries/helix-queues-setup.yml |
Updated Debian helix queue references for linux_arm (ARM32) and linux_x64 (AMD64) platforms |
eng/pipelines/coreclr/templates/helix-queues-setup.yml |
Updated Debian helix queue references for linux_arm (ARM32) platform in both public and internal project configurations |
Member
|
I'm going to close this until we make a decision on #122360 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes Issue
main PR
Description
Updates helix queue configurations from Debian 12 to Debian 13 across coreclr and libraries pipeline templates. Changes include:
Debian.12.*→Debian.13.*debian-12-helix-*→debian-13-helix-*Files modified:
eng/pipelines/coreclr/templates/helix-queues-setup.yml(ARM32 queues)eng/pipelines/libraries/helix-queues-setup.yml(ARM32 and AMD64 queues)Customer Impact
No direct customer impact. Infrastructure update to align helix test queues with current Debian release.
Regression
No. This is a forward-looking infrastructure update.
Testing
Configuration change only. Validated queue name and container image tag consistency across all references.
Risk
Low. Syntactically equivalent changes to queue configuration strings. Assumes corresponding Debian 13 helix infrastructure is deployed.
Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.