chore: enable automatic CHANGELOG generation via Changesets#945
Draft
kdaviduik wants to merge 2 commits into03-09-feat_migrate_yarn_v1_to_pnpmfrom
Draft
chore: enable automatic CHANGELOG generation via Changesets#945kdaviduik wants to merge 2 commits into03-09-feat_migrate_yarn_v1_to_pnpmfrom
kdaviduik wants to merge 2 commits into03-09-feat_migrate_yarn_v1_to_pnpmfrom
Conversation
This was referenced Mar 9, 2026
Contributor
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Switch from manual CHANGELOG management to @changesets/changelog-github. - Update .changeset/config.json to use @changesets/changelog-github - Pass GITHUB_TOKEN to changeset version step in release workflow (@changesets/changelog-github needs it to fetch PR metadata for links) - Fix git add to include CHANGELOG.md (pre-existing bug — changeset version modifies CHANGELOG.md but it was never staged in the commit step) - Fix stale v3.0.6 '(Unreleased)' label — published to npm August 25, 2025
…ELOG date Two items from the PR 4a plan that were missed in the original commit: 1. @changesets/changelog-github was referenced in .changeset/config.json but never declared in package.json devDependencies. The lockfile had the specifier (from pnpm install), so CI's --frozen-lockfile saw a mismatch and failed. 2. CHANGELOG.md v3.0.6 date was still "(Unreleased)" — v3.0.6 was published to npm on August 25, 2025.
kdaviduik
force-pushed
the
enable-auto-changelog
branch
from
f2a1c65 to
b8b74d9
Compare
kdaviduik
force-pushed
the
03-09-feat_migrate_yarn_v1_to_pnpm
branch
from
a65405e to
12b544b
Compare
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
1 participant
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.
Switch from manual CHANGELOG management to @changesets/changelog-github.
(@changesets/changelog-github needs it to fetch PR metadata for links)
modifies CHANGELOG.md but it was never staged in the commit step)
Verification
Smoke-tested the CHANGELOG automation locally:
@shopify/buy-button-js: patch)GITHUB_TOKEN=$(gh auth token) pnpm exec changeset version## 3.0.7section containing the test entrygit checkout -- package.json CHANGELOG.md && rm .changeset/test-changelog-automation.md)Result:
changeset versionexits 0, plugin loads correctly, and CHANGELOG.md is generated with proper formatting.