[goosewobbler]

Description

publish --input validated its input with z.object schemas, which strip undeclared keys. updates[].tag and baselineTags were lost, so per-package mode never ran and baseline tags were never created. Any other VersionOutput field the schema didn't list was lost too. release and standing-pr publish pass the output in memory and were unaffected.

The schemas now use z.looseObject and declare tag and baselineTags. A round-trip test checks that a fully populated VersionOutput comes back from parseInput unchanged.

Keeping the tags lets publish --input reach per-package mode, which had two gaps: baseline tags were never pushed, and under --skip-publish nothing was pushed and no GitHub releases were created. The final push stage now also runs in per-package mode, after every package has published, so it adds the remaining tags (or pushes everything under --skip-publish). That also fixes baseline tags for release and standing-pr publish in per-package mode, which had the same gap.

The push stage also pushed every local tag (git push --tags), in batch mode too. It now pushes only the tags this run recorded, each by explicit ref.

Related Issue(s)

Closes #675

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

New input.spec.ts tests cover per-package and baseline tags surviving parseInput, rejection of a non-string tag, and a full round-trip; all three fail on the old schema. The round-trip fixture is typed with Required<…>, so a new VersionOutput field is a type error in the editor until the fixture includes it. CI won't catch that, because publish's typecheck excludes test files.

pipeline.spec.ts: per-package mode runs the final push once, after the last package tag, and not when a package fails; per-package input with skipPublish still pushes and creates GitHub releases. Both fail with the old guard.

parseInput's body is untouched, so #616 should rebase cleanly.

🤖 Generated with Claude Code

Confidence Score: 5/5

The PR appears safe to merge; the unrelated-tag push is fixed and no new blocking issues were found.

Summary

The PR keeps per-package and baseline tags when reading publish input, then pushes baseline tags after all packages succeed.

• Publish input keeps package and baseline tags.
• Per-package runs push the remaining tags after publishing succeeds.

_{Reviews (3) · Last reviewed commit: "fix(publish): push only this release's t..." · Reviewed by Greptile}

[github-actions]

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

Release Preview — v0.41.2 → v0.41.3

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.41.3

Changed

• fix the skipped-bump entries (troubleshooting) (PR #695)

Fixed

• trim push-stage comments (publish)
• drop redundant schema comment (publish)
• push only this release's tags (publish)
• push baseline tags, and push at all under --skip-publish, in per-package mode (publish)
• keep per-package and baseline tags in --input (publish) (#675)

All packages → 0.41.3 (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.41.3	0.42.0

---

Updated automatically by ReleaseKit

[goosewobbler]

@greptileai review plz