Uh oh!
There was an error while loading. Please reload this page.
[ci] Attribute backport changelog entries to original PR author - #2091
Merged
Conversation
`@changesets/changelog-github` resolves a changeset commit to its associated PR via the GitHub GraphQL `associatedPullRequests` field. For commits landed on `stable` via our backport workflow, that resolves to the backport PR authored by `github-actions[bot]` (since the backport workflow uses `createCommitOnBranch` to produce signed commits), so the generated changelog ends up with "Thanks @github-actions!" instead of the original contributor. This adds a small `.changeset/changelog.mjs` wrapper around `@changesets/changelog-github` that detects backport PRs by matching the title (`Backport #N: ...`) or body (`Automated backport of #N to ` + '`stable`' + `...`) produced by `.github/workflows/backport.yml`, resolves the original PR number, and injects `pr:`/`commit:` directives into the changeset summary before delegating to the upstream generator. The result is that the rendered changelog entry attributes the change to the original PR and author, while the commit link still points at the backport commit on the release branch.
|
Contributor
Contributor
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 1 step💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 25 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 50 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.all with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.race with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 10 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 25 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 50 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 10 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 25 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 50 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Stream Benchmarks(includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro stream pipeline with 5 transform steps (1MB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro 10 parallel streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro fan-out fan-in 10 streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
❌ Some benchmark jobs failed:
Check the workflow run for details. |
Contributor
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests▲ Vercel Production (1 failed)sveltekit (1 failed):
Details by Category❌ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
❌ Some E2E test jobs failed:
Check the workflow run for details. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR customizes the Changesets GitHub changelog generator so that changeset entries created via the stable backport workflow are attributed to the original PR author (instead of the backport PR authored by github-actions[bot]), while still linking to the backport commit on the release branch.
Changes:
- Switches Changesets config to use a local changelog generator wrapper instead of
@changesets/changelog-githubdirectly. - Adds
.changeset/changelog.mjswrapper that detects backport PRs (by title/body patterns) and injectspr:+commit:directives to force attribution to the original PR.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.changeset/config.json | Points Changesets at the new local changelog generator wrapper. |
.changeset/changelog.mjs | Implements backport PR detection and summary rewriting before delegating to @changesets/changelog-github. |
Comments suppressed due to low confidence (1)
.changeset/changelog.mjs:182
- Same issue here: logging
${err.message}can throw if a non-Error (or null/undefined) is thrown. Use a safe formatter (e.g.(err instanceof Error ? err.message : String(err))) to ensure this fallback path never introduces a new failure.
} catch (err) {
console.warn(
`[changelog] failed to look up PR #${prNumber}: ${err.message}`,
);
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
VaguelySerious
approved these changes
May 22, 2026
- Use `Bearer` instead of `Token` for the GitHub GraphQL auth header for consistency with the rest of the repo (Copilot review on PR #2091). - Add a defensive `formatError` helper so `console.warn` in the catch blocks doesn't itself throw when a non-Error value is thrown (Copilot review on PR #2091).
Uh oh!
There was an error while loading. Please reload this page.
github-actionsBot
added a commit
that referenced
this pull request
May 22, 2026
* [ci] Attribute backport changelog entries to original PR author `@changesets/changelog-github` resolves a changeset commit to its associated PR via the GitHub GraphQL `associatedPullRequests` field. For commits landed on `stable` via our backport workflow, that resolves to the backport PR authored by `github-actions[bot]` (since the backport workflow uses `createCommitOnBranch` to produce signed commits), so the generated changelog ends up with "Thanks @github-actions!" instead of the original contributor. This adds a small `.changeset/changelog.mjs` wrapper around `@changesets/changelog-github` that detects backport PRs by matching the title (`Backport #N: ...`) or body (`Automated backport of #N to ` + '`stable`' + `...`) produced by `.github/workflows/backport.yml`, resolves the original PR number, and injects `pr:`/`commit:` directives into the changeset summary before delegating to the upstream generator. The result is that the rendered changelog entry attributes the change to the original PR and author, while the commit link still points at the backport commit on the release branch. * Address review feedback - Use `Bearer` instead of `Token` for the GitHub GraphQL auth header for consistency with the rest of the repo (Copilot review on PR #2091). - Add a defensive `formatError` helper so `console.warn` in the catch blocks doesn't itself throw when a non-Error value is thrown (Copilot review on PR #2091). Signed-off-by: Nathan Rajlich <n@n8.io>
Contributor
Backport PR opened against |
TooTallNate pushed a commit
that referenced
this pull request
May 22, 2026
… (#2092) * [ci] Attribute backport changelog entries to original PR author `@changesets/changelog-github` resolves a changeset commit to its associated PR via the GitHub GraphQL `associatedPullRequests` field. For commits landed on `stable` via our backport workflow, that resolves to the backport PR authored by `github-actions[bot]` (since the backport workflow uses `createCommitOnBranch` to produce signed commits), so the generated changelog ends up with "Thanks @github-actions!" instead of the original contributor. This adds a small `.changeset/changelog.mjs` wrapper around `@changesets/changelog-github` that detects backport PRs by matching the title (`Backport #N: ...`) or body (`Automated backport of #N to ` + '`stable`' + `...`) produced by `.github/workflows/backport.yml`, resolves the original PR number, and injects `pr:`/`commit:` directives into the changeset summary before delegating to the upstream generator. The result is that the rendered changelog entry attributes the change to the original PR and author, while the commit link still points at the backport commit on the release branch. * Address review feedback - Use `Bearer` instead of `Token` for the GitHub GraphQL auth header for consistency with the rest of the repo (Copilot review on PR #2091). - Add a defensive `formatError` helper so `console.warn` in the catch blocks doesn't itself throw when a non-Error value is thrown (Copilot review on PR #2091). Signed-off-by: Nathan Rajlich <n@n8.io> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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 freeto 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.
Summary
@changesets/changelog-githubresolves a changeset commit to its associated PR via the GitHub GraphQLassociatedPullRequestsfield. For commits that landed onstablevia the backport workflow, that resolves to the backport PR authored bygithub-actions[bot](since.github/workflows/backport.ymluses GraphQLcreateCommitOnBranchto produce signed commits), so the generated changelog ends up withThanks @github-actions!instead of the original contributor. See e.g. theThanks @github-actions!lines in the diff for #1921.This adds a small wrapper at
.changeset/changelog.mjsaround@changesets/changelog-githubthat:@changesets/get-github-info's own selection logic).Backport #N: ...) or body (e.g.Automated backport of #N to `stable` ...) — both formats produced by.github/workflows/backport.yml.pr: #<original>andcommit: <backportSha>directives into the changeset summary before delegating to the upstream generator. Both directives are documented@changesets/changelog-githubfeatures.The result: the rendered changelog entry attributes the change to the original PR and author (e.g.
Thanks @pranaygp!with a link to PR #2046) while the commit link still points at the backport commit on the release branch.Non-backport commits, commits without an associated PR, and any lookup failures all fall through to plain upstream delegation — a flaky network call can never break
pnpm changeset version.Loaded via Node's
require(esm)(the release workflow uses Node 24 which supports it).Verification
Verified end-to-end on a
stableworktree by runningpnpm changeset versionand inspecting the rendered changelog. The new 4.2.5 section inpackages/core/CHANGELOG.mdrendered as:All five entries that previously rendered as
Thanks @github-actions!(see the diff in #1921) now correctly attribute to the original PR and author. Non-backport entries are unchanged.No changeset entry is required — this is a release-tooling-only change with no impact on published packages.