Skip to content

fix(release): set git identity for annotated tags - #53

Merged
SutuSebastian merged 1 commit into
mainfrom
fix/release-git-identity
Aug 8, 2026
Merged

fix(release): set git identity for annotated tags#53
SutuSebastian merged 1 commit into
mainfrom
fix/release-git-identity

Conversation

@SutuSebastian

Copy link
Copy Markdown
Contributor

Summary

  • Release failed after publishing @stainless-code/preact-layers@0.2.4: git tag -a needs user.name/user.email; changesets/action commitMode: github-api does not set them.
  • Configure identity in the workflow + scripts/release.ts; on skip (already published), still ensure the tag so retries recover; sort package dirs for deterministic order.

Test plan

  • Merge → Release re-runs on main
  • Remaining packages publish; preact skipped + tagged
  • Tags / GitHub Releases for new versions

Publish succeeded then died on `git tag -a` with empty committer; configure identity and still tag on skip so partial retries recover.
@changeset-bot

changeset-bot Bot commented Aug 8, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: cb03f22

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

@coderabbitai

coderabbitai Bot commented Aug 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@SutuSebastian, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 90842565-1e5a-4b24-be18-9b56b246acb5

📥 Commits

Reviewing files that changed from the base of the PR and between 6acaea0 and cb03f22.

📒 Files selected for processing (3)
  • .agents/lessons.md
  • .github/workflows/release.yml
  • scripts/release.ts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@SutuSebastian
SutuSebastian merged commit 58ceff8 into main Aug 8, 2026
15 checks passed
@SutuSebastian
SutuSebastian deleted the fix/release-git-identity branch August 8, 2026 11:09
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