-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ci: repair release/stable/9.0 build against current SDKs & runner images #3408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
dansiegel
wants to merge
4
commits into
release/stable/9.0
Choose a base branch
from
claude/release-9-0-build-fix-5acca1
base: release/stable/9.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+34
−1
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6722683
ci: fix release/stable/9.0 build against current SDK & runner images
dansiegel faa2784
ci: roll test host forward so net6.0 tests run on current runners
dansiegel 3b0a156
build: pin SDK to 8.0.x so the net8.0 workload targets build
dansiegel 9f28bcf
test: make AsyncDelegateCommand cancellation test deterministic
dansiegel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pinning only the
Prism CIForms job leaves the release path on the template default runner. I checked.github/workflows/start-release.yml:37-45, and its identicalbuild-prism-formsreusable workflow call still omitsruns-on; the v1 template defaults that input towindows-latest, which this change identifies as missing the Xamarin.Android targets. WhenStart NuGet Releaseis manually run forrelease/stable/9.0, Forms packaging will still hit the same missingMonoAndroid13.0targets, so the release workflow needs the sameruns-on: windows-2022pin.Useful? React with 👍 / 👎.