docs(release-batching): recommend a new release when commits sit past the latest tag
Adds one paragraph to the release-batching reference. Before any decision to publish, the agent checks every package for commits past its latest release tag and recommends a new release first when there are any. The paragraph covers public and private packages and a republish of an existing tag, which ships the tagged content without the later commits. The recommendation names how many commits are unreleased, what they change and the version the repository's scheme gives them. It does not permit tagging, publishing or announcing, and it does not hold a ready batch for unrelated work.
This records the user's standing preference to recommend a new release whenever commits sit past the release tag, for all packages. The change is in rules/references/release-batching.md plus a changelog entry. The release-batching modifier and the README row needed no edit.
This pull request is independent of the 0.13.0 release pull request. Landing the release pull request first keeps this entry out of the 0.13.0 notes, so rebase this one onto the release commit and its entry stays under Unreleased.
Checks: node --test test/*.test.mjs, bun test test/ skills/ (516 pass, 8 skip, 0 fail), npm run check:package -- --bun, oxlint (one existing warning in test/install-ps1.test.mjs), oxfmt --check. Plain-prose check on the added text is clean.
Summary by cubic
Records the standing preference to recommend a new release whenever any package has commits past its latest release tag, before any decision to publish. The recommendation names how many commits are unreleased, what they change, and the version the repository's scheme assigns.
- Covers public and private packages, and republishing an existing tag, which ships the tagged content without the later commits.
- For a package that has never been tagged, state there is no baseline and treat the publish as its first release.
- The recommendation does not permit tagging, publishing, or announcing, and does not hold a ready batch for unrelated work.
- This is independent of the 0.13.0 release; if that lands first, rebase so this changelog entry stays under Unreleased.
Summary by CodeRabbit
- Documentation
- Clarified release-batching guidance to check public and private packages for commits newer than their latest release tags before deciding whether to publish, including when republishing an existing tag.
- When newer commits are found, the guidance recommends releasing first and reporting the commit count, changes, and combined version. Packages without a release tag are identified as having no baseline and treated as first releases.
- The recommendation does not authorize tagging, publishing, or announcing, and does not delay a ready batch for unrelated work.