Run & review this pull request in StackBlitz Codeflow.

⚠️ No Changeset found

Latest commit: 0028041

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.

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

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hey-api-docs	Ready	Preview, Comment	Apr 13, 2026 8:31am

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 40.04%. Comparing base (6e20279) to head (0028041).
⚠️ Report is 4 commits behind head on main.

@@           Coverage Diff           @@
##             main    #3748   +/-   ##
=======================================
  Coverage   40.04%   40.04%           
=======================================
  Files         520      520           
  Lines       19243    19243           
  Branches     5726     5726           
=======================================
  Hits         7705     7705           
  Misses       9342     9342           
  Partials     2196     2196           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

TL;DR — Fixes release notes generation by filtering out GitHub App contributors (app/ prefixed usernames), adding a fallback message when no contributors are found, resolving the release commit SHA for GitHub Releases, and overhauling date-based snapshot tag resolution to correctly extract per-package versions.

Key changes

• Filter app/ contributors from release notes — Excludes GitHub App accounts (e.g. app/github-actions) from the contributors list so only real users appear.
• Add fallback message for empty contributors — When no contributors exist for a release, shows a "Be the first to contribute" call-to-action instead of a missing section.
• Resolve release commit for target_commitish — Looks up the actual ci: release commit SHA so the GitHub Release points at the correct commit rather than the workflow's github.sha.
• Overhaul snapshot/date-tag resolution in tags.ts — Introduces multi-strategy lookup (commit changelog inspection → same-day release commit → ancestry-based → root CHANGELOG.md parsing) to recover per-package versions from date-based tags that lack embedded version info.
• Add CHANGELOG.md entry for the 2026-04-13 release — Documents the latest release across 7 packages with breaking changes, plugin updates, and new features.

_{Summary ｜ 5 files ｜ 1 commit ｜ base: main ← ci/fix-release-notes-contributors}

Filtering GitHub App contributors

Before: GitHub App accounts like app/github-actions could appear in the contributors list.
After: Any username starting with app/ is excluded alongside bots and maintainers.

A single guard (!github.startsWith('app/')) is added to the contributor filter chain in getContributorsFromPullRequests.

scripts/changelog/contributors.ts

Empty contributors fallback and section restructuring

Before: The "Contributors" heading was only emitted when at least one contributor existed — an empty release had no contributors section at all.
After: The heading always appears. When no contributors are found, a link to open issues invites new contributions.

The ## Contributors heading is moved outside the if (contributors.length) block, and an else branch adds the call-to-action.

scripts/changelog/release-notes.ts

Release commit resolution in the workflow

Before: softprops/action-gh-release used the implicit github.sha as the target commit for the release.
After: A new "Resolve Release Commit" step greps git log for the ci: release commit and passes its SHA via target_commitish, falling back to github.sha if not found.

This ensures the GitHub Release tag points at the actual release commit rather than whatever commit triggered the workflow.

.github/workflows/release.yml

Overhauled date-based snapshot tag resolution

Before: getGitTags only handled <package>@<version> and v<version> tag formats — date-based tags (e.g. 2026-04-13) were ignored.
After: A new getSnapshotReleaseTags function implements a four-tier fallback strategy to extract per-package versions from date tags.

The resolution cascade:

Results are deduplicated via a Map keyed by date:packageName:version, preferring the most recent timestamp.

Why are regex patterns hoisted to module scope?

The six patterns (`packageTagPattern`, `legacyTagPattern`, `releaseDatePattern`, `changelogDateHeadingPattern`, `changelogPackageHeadingPattern`, `changelogVersionHeadingPattern`) are compiled once and reused across iterations rather than being recreated per tag — a minor performance improvement when processing many tags.

scripts/changelog/tags.ts

  ^{｜ View workflow run ｜ Triggered by Pullfrog ｜ 𝕏}