[goosewobbler]

Description

Standalone publish couldn't resume after a failure past the commit stage: the re-run found nothing to commit and failed at git commit before any later stage was retried.

• Commit stage: after git add, if nothing is staged and HEAD's subject matches the release commit message, it reuses HEAD and goes on to tagging (tags already at HEAD were already skipped). If nothing is staged and HEAD isn't the release commit, it throws GIT_COMMIT_ERROR naming both subjects. A dry run skips the add, so it commits as before.
• changed stays accurate: git.committed stays false for a reused commit, so publishDidChange counts only what the re-run did.
• Branch push on resume: the pipeline context tracks "release commit reused" separately, and the push stages push the branch when the commit was created or reused. The standing-PR path (skipGitCommit) is unchanged and still pushes tags only.
• @releasekit/git: new hasStagedChanges() (diff --cached --quiet) on Git, GitCli and FakeGit.
• Docs: docs/cli.md describes resuming instead of "isn't supported yet".

Related Issue(s)

Closes #707.

Type of Change

• feat — New feature
• fix — Bug fix
• docs — Documentation change
• refactor — Code refactoring
• test — Adding or updating tests
• chore — Maintenance, dependencies, tooling
• Breaking change — Requires major version bump

Scope

• @releasekit/version
• @releasekit/notes
• @releasekit/publish
• @releasekit/release
• @releasekit/config
• @releasekit/core
• CI / workflows
• Root / monorepo

Checklist

• Lint passes (pnpm lint)
• Tests pass (pnpm test)
• Typecheck passes (pnpm typecheck)
• Documentation updated (if applicable)
• Breaking changes noted in description

Testing Notes

• test/integration/resume-publish.spec.ts uses real git and a bare remote. The first releasekit publish --input fails at the push (exit 9, changed: true); after origin is fixed, the re-run succeeds with changed: false. It asserts exactly one release commit, and that the branch and v0.2.0 reached the remote at HEAD. It fails without the fix: at git commit, or on the missing remote branch with only the commit-stage change.
• Unit tests: the commit stage (reuse, a missing tag created on the reused commit, a multi-line message matched on its subject, the throw when HEAD isn't the release commit, dry run); the branch push for a reused commit in runGitPushStage, preparePushSetup and pushPackageTag; publishDidChange false for a reused commit; hasStagedChanges in GitCli and FakeGit.
• Full gate (lint, typecheck, tests) and the integration suite pass.

🤖 Generated with Claude Code

Confidence Score: 5/5

The PR appears safe to merge; the previous multiline-message issue is fixed.

Summary

Allows a partial publish to resume by reusing the release commit.

• A publish rerun reuses the release commit when it is already at HEAD.
• A rerun that reuses the release commit also pushes its branch.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Stage release files] --> B{Any staged changes?}
  B -->|Yes| C[Create release commit]
  B -->|No| D{HEAD subject matches?}
  D -->|No| E[Stop with commit error]
  D -->|Yes| F[Reuse release commit]
  C --> G[Create missing tags]
  F --> G
  G --> H[Continue publishing and push branch and tags]

Loading

_{Reviews (2) · Last reviewed commit: "fix(publish): compare the release commit..." · Reviewed by Greptile}

[github-actions]

Standing release PR: #614 · v0.42.0 queued (4 packages) · open 82d 20h 45m · ✅ ready to merge

Release Preview — v0.41.2 → v0.42.0

Note: Labels on this PR are advisory in standing-pr mode. Bumps come from conventional commits in the standing PR; override by editing labels on the standing PR itself. Add release:immediate to bypass the standing PR and release this PR directly.

These changes will be added to the release PR (#614) when merged:

Changelog

monorepo 0.41.2 → 0.42.0

Changed

• reword the resume comments for clarity
• format the resume test and simplify the subject helper

Fixed

• BREAKING apply schema publish defaults when the config has no publish block (publish) (PR #690 · closes #667)
• compare the release commit by git's subject rules (publish)
• resume a partial publish by reusing the release commit (publish) (#707)

All packages → 0.42.0 (sync versioning)

• @releasekit/version
• @releasekit/notes
• @releasekit/publish
• @releasekit/release

After merge — predicted release

No version escalation — this PR's changes will be included in the queued release without affecting the projected versions.

Package	Standing PR	This PR	After merge
monorepo	0.42.0	0.42.0	0.42.0

---

Updated automatically by ReleaseKit