Skip to content

fix aggregate changelog changeset commit lookup#7704

Draft
bdbch wants to merge 1 commit intomainfrom
fix/aggregate-changeset-commit
Draft

fix aggregate changelog changeset commit lookup#7704
bdbch wants to merge 1 commit intomainfrom
fix/aggregate-changeset-commit

Conversation

@bdbch
Copy link
Copy Markdown
Member

@bdbch bdbch commented Apr 4, 2026

Changes Overview

Use Changesets' git helper to resolve the commit for each changeset when generating the aggregated changelog.

Implementation Approach

Replaced the custom per-file git log lookup with @changesets/git's getCommitsThatAddFiles() and kept the legacy changes.json fallback for older changesets.

Testing Done

Ran node --check scripts/aggregate-changeset.js.

Verification Steps

  1. Run the aggregate changelog script for a release plan that includes one or more changesets.
  2. Confirm the generated aggregated changelog links each entry to the commit or PR associated with that changeset rather than the repository's latest commit.

Additional Notes

This keeps commit resolution aligned with Changesets' own git utilities, including shallow clone handling.

Checklist

  • I have created a changeset for this PR if necessary.
  • My changes do not break the library.
  • I have added tests where applicable.
  • I have followed the project guidelines.
  • I have fixed any lint issues.

Related Issues

@netlify
Copy link
Copy Markdown

netlify bot commented Apr 4, 2026

Deploy Preview for tiptap-embed ready!

Name Link
🔨 Latest commit 52f8711
🔍 Latest deploy log https://app.netlify.com/projects/tiptap-embed/deploys/69d1154971ee7e0008e72b36
😎 Deploy Preview https://deploy-preview-7704--tiptap-embed.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 4, 2026

⚠️ No Changeset found

Latest commit: 52f8711

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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