Skip to content

ci: resolve the shared build pipeline at job time and use .NET 11 - #73

Merged
kieronlanning merged 2 commits into
mainfrom
ci/unpin-purview-build
Nov 16, 2026
Merged

kieronlanning merged 2 commits into
mainfrom
ci/unpin-purview-build

Conversation

@kieronlanning

Copy link
Copy Markdown
Contributor

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.

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.
@kieronlanning
kieronlanning merged commit 86df72d into main Nov 16, 2026
1 check passed
@kieronlanning
kieronlanning deleted the ci/unpin-purview-build branch November 16, 2026 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant