Skip to content

Apply open dependency bumps and rename publish workflows after their destination - #54

Merged
xavierjohn merged 2 commits into
mainfrom
chore/dependency-bumps
Aug 18, 2026
Merged

Apply open dependency bumps and rename publish workflows after their destination#54
xavierjohn merged 2 commits into
mainfrom
chore/dependency-bumps

Conversation

@xavierjohn

@xavierjohn xavierjohn commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Consolidates the four open Dependabot version-bump PRs (#43, #47, #48, #51) and renames the publish workflows after their destination.

Dependency bumps

Package / action From To
actions/setup-dotnet v5 v6
OpenTelemetry.Exporter.OpenTelemetryProtocol 1.16.0 1.17.0
OpenTelemetry.Extensions.Hosting 1.16.0 1.17.0
OpenTelemetry.Instrumentation.AspNetCore 1.16.0 1.17.0
OpenTelemetry.Instrumentation.Http 1.16.0 1.17.0
OpenTelemetry.Instrumentation.Runtime 1.15.1 1.17.0
Nerdbank.GitVersioning 3.10.85 3.10.91

Why consolidate instead of merging the four PRs

#47 and #48 each bumped a single OpenTelemetry package. The repo's documented policy is that the OTel packages move as a set, so merging either one as proposed would have left the set split across versions — the exact state the policy exists to prevent. Bumping all five together is the only way to honour it.

While doing that, the policy comment in Directory.Packages.props turned out to be already stale: it claimed the contrib Instrumentation.* packages stay on 1.15.x, but .AspNetCore and .Http were both already on 1.16.0 — only .Runtime still lagged. The comment has been rewritten to describe what the repo actually does.

Verification

  • Confirmed on nuget.org that 1.17.0 is published for all five OTel packages (a set bump is only safe if the whole set exists at the target version).
  • Confirmed nbgv 3.10.91 leaves the version scheme intact by packing: still 0.1.0-alpha.<height>.g<sha>.
  • setup-dotnet@v6 is exercised by this PR's own CI run, which is the real proof for that one.
  • Full build (0 warnings) and all 352 tests pass.

Publish workflow rename

Before After Display name
publish.yml publish-nuget-org.yml Publish to NuGet.org
publish-alpha.yml publish-github-packages.yml Publish to GitHub Packages

Mirrors the rename made in the framework repo (xavierjohn/Trellis#700), so both repositories name these workflows the same way.

Both workflows publish the same version — the only real difference is the feed they push to (api.nuget.org with NUGET_API_KEY, vs nuget.pkg.github.com with GITHUB_TOKEN). The old names implied the distinction was stable-vs-alpha, so choosing the right one from the Actions list meant opening the file to check which feed it actually targeted. Naming them after the destination removes that step. Cross-references in each file's header comment were updated to match.

This is folded into this PR rather than stacked on top of it, because both changes touch the same two workflow files and keeping them apart only created a merge-order requirement.

Also: drops an inert flag

The GitHub Packages workflow passed --version-suffix "alpha.${{ github.run_number }}" to dotnet pack. That flag is silently ignored, because nbgv sets PackageVersion explicitly — a suffix only applies when the version is left open-ended.

Verified rather than assumed: packing with --version-suffix "alpha.999" still produced Trellis.Yarp.0.1.0-alpha.71.gb09de4b2d0.nupkg. Since it never had any effect, the step is now just Pack. (Same latent bug the framework repo had.)

Notes

…bgv 3.10.91)

Consolidates the four open Dependabot PRs (#43, #47, #48, #51). Two of them
could not be merged as proposed without leaving the tree in a state the
existing version-policy comment explicitly forbids, so they are applied
together with the rest of their package set.

OpenTelemetry -> 1.17.0 (supersedes #47 and #48).
  #47 bumped only Exporter.OpenTelemetryProtocol and #48 only
  Instrumentation.Runtime. Taking either alone would split the set: the
  comment in Directory.Packages.props records that core (Exporter +
  Extensions.Hosting) tracks a single line, so moving Exporter to 1.17.0
  while Extensions.Hosting stayed at 1.16.0 would violate it.

  A matching 1.17.0 now exists for ALL five packages (verified against
  nuget.org), so the whole set is unified. This also clears pre-existing
  drift: Instrumentation.Runtime was still on 1.15.1 while
  Instrumentation.AspNetCore and .Http had already moved to 1.16.0 --
  which the comment claimed was not the case. The comment is rewritten to
  describe the actual policy: unify when a matching release exists across
  the set, and let contrib packages sit on their own latest when they lag,
  rather than forcing a lockstep version that has no matching release.

Nerdbank.GitVersioning 3.10.85 -> 3.10.91 (#43).
  Verified the version scheme is unaffected: packing still yields
  0.1.0-alpha.70.g7f3861c59d computed from the head commit.

actions/setup-dotnet v5 -> v6 (#51).
  All four workflows use the global-json-file input, which is unchanged
  across the major, so the bump is uniform.

Build clean, 352 tests passing.
Copilot AI lite review requested due to automatic review settings August 18, 2026 05:47
@github-actions

github-actions Bot commented Aug 18, 2026

Copy link
Copy Markdown

Test Results

352 tests  ±0   352 ✅ ±0   44s ⏱️ -15s
  4 suites ±0     0 💤 ±0 
  4 files   ±0     0 ❌ ±0 

Results for commit 76272f7. ± Comparison against base commit 7f3861c.

♻️ This comment has been updated with latest results.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Consolidates several Dependabot updates into a single, consistent dependency bump set for this repo, covering NuGet central package versions and GitHub Actions workflows.

Changes:

  • Bumped Nerdbank.GitVersioning from 3.10.85 to 3.10.91.
  • Unified the sample’s OpenTelemetry package set to 1.17.0 and updated the accompanying version-policy comment.
  • Upgraded all workflows from actions/setup-dotnet@v5 to @v6.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
Directory.Packages.props Updates central NuGet versions (nbgv + OpenTelemetry set) and refreshes the versioning policy comment.
.github/workflows/build.yml Uses actions/setup-dotnet@v6 for CI build.
.github/workflows/codeql.yml Uses actions/setup-dotnet@v6 for CodeQL workflow.
.github/workflows/publish.yml Uses actions/setup-dotnet@v6 for package publishing workflow.
.github/workflows/publish-alpha.yml Uses actions/setup-dotnet@v6 for alpha publishing workflow.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.


- name: Setup .NET
uses: actions/setup-dotnet@v5
uses: actions/setup-dotnet@v6
@@ -20,7 +20,7 @@ jobs:
fetch-depth: 0 # needed for nbgv

- name: Setup .NET
uses: actions/setup-dotnet@v5
uses: actions/setup-dotnet@v6

- name: Setup .NET
uses: actions/setup-dotnet@v5
uses: actions/setup-dotnet@v6
@@ -27,7 +27,7 @@ jobs:
fetch-depth: 0 # needed for nbgv

- name: Setup .NET
uses: actions/setup-dotnet@v5
uses: actions/setup-dotnet@v6
Mirrors the same change made in the framework repo (xavierjohn/Trellis#700).

publish.yml       -> publish-nuget-org.yml        "Publish to NuGet.org"
publish-alpha.yml -> publish-github-packages.yml  "Publish to GitHub Packages"

Both workflows publish the same version; the only real difference is the
feed they push to. The old names implied the distinction was stable vs
alpha, so picking the right one from the Actions list meant opening the
file to check which feed it targeted. Naming them after the destination
removes that step. Cross-references in the header comments were updated to
match.

Also drops an inert flag from the GitHub Packages workflow:
--version-suffix "alpha.${{ github.run_number }}" is silently ignored,
because nbgv sets PackageVersion explicitly. Verified by packing with
--version-suffix "alpha.999" and still getting 0.1.0-alpha.71.gb09de4b2d0.
Since it never had any effect, the step is just "Pack" now.

Renaming a workflow file detaches its run history under the old name in
the Actions UI. That is expected and cosmetic.

Stacked on chore/dependency-bumps (#54) because that PR also edits both of
these files; merge #54 first to avoid a rename/modify conflict.
@xavierjohn xavierjohn changed the title Apply open dependency bumps (setup-dotnet v6, OpenTelemetry 1.17.0, nbgv 3.10.91) Apply open dependency bumps and rename publish workflows after their destination Aug 18, 2026
@xavierjohn
xavierjohn merged commit b7b48bb into main Aug 18, 2026
4 checks passed
@xavierjohn
xavierjohn deleted the chore/dependency-bumps branch August 18, 2026 06:08
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.

2 participants