Repository navigation
ci: resolve the shared build pipeline at job time and use .NET 11 - #73
Merged
Merged
Conversation
Both the PR gate and the release pinned Purview.Build at 0.8.1 while the shared pipeline has moved to 0.9.1, so this repository was running a two-versions-stale gate - and the release failed in CreateGitHubReleaseModule for it. The version is now omitted, which is what the reusable workflow documents: the latest stable Purview.Build is installed at job time. The SDK the pipeline installs is still pinned, at 11.0.x: the runner image's .NET drifts between builds, and the projects this site documents target net11.0. There is no global.json here, so this input is the one that decides. Release gains workflow_dispatch so a failed release can be retried without a package.json change, which is the only other way the workflow is triggered.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ci: resolve the shared build pipeline at job time and use .NET 11
Both the PR gate and the release pinned Purview.Build at 0.8.1 while the shared
pipeline has moved to 0.9.1, so this repository was running a two-versions-stale
gate - and the release failed in CreateGitHubReleaseModule for it. The version is
now omitted, which is what the reusable workflow documents: the latest stable
Purview.Build is installed at job time.
The SDK the pipeline installs is still pinned, at 11.0.x: the runner image's .NET
drifts between builds, and the projects this site documents target net11.0. There
is no global.json here, so this input is the one that decides.
Release gains workflow_dispatch so a failed release can be retried without a
package.json change, which is the only other way the workflow is triggered.