[ci] Publish VS workload zips (#9870) #9882
Merged
Conversation
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
Context: xamarin/yaml-templates@96d7858 Adds the VS manifest zips needed by the workload versions VS insertion pipeline to Maestro publishing. The first update to VS that includes these changes will have to be done manually, as the manifest names are also changing to work with the new pipeline.
I'd like for our next VS insertion for .NET 9 (and related changes from maui and macios) to include these changes -- we'll need to do one manual VS update against these new manifests to transition to the new workload sets insertion workflow |
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.
Context: https://github.com/xamarin/yaml-templates/commit/96d7858cce242c5eea76028f3f051bb9ffda793c
Adds the VS manifest zips needed by the workload versions VS insertion
pipeline to Maestro publishing.
The first update to VS that includes these changes will have to be done
manually, as the manifest names are also changing to work with the new
pipeline.