Release v3.1.0

[flyingrobots]

Summary

• set @git-stunts/plumbing package version to 3.1.0
• promote the safe prune inspection notes to the dated 3.1.0 changelog section

Release rationale

This minor release publishes the additive streamed prune-inspection API delivered for #6, unblocking git-stunts/git-cas#49 and git-stunts/git-cas#55.

Verification

• npm run lint
• npm test (Node, Bun, Deno; Deno 210 steps)
• npm pack --dry-run (@git-stunts/plumbing@3.1.0, 57 files)
• Graft review: two release-metadata files; no exported API delta in this PR

Refs #6

[flyingrobots]

Self-review

Result: no blocking findings.

Reviewed the complete main..f3594ef diff and the tag-triggered publish workflow. The branch changes only the authoritative npm version and the matching dated changelog heading. npm pack --dry-run identifies the artifact as @git-stunts/plumbing@3.1.0 and includes the newly merged API. ESLint and the full Node/Bun/Deno matrix pass.

The root version recorded in package-lock.json has remained 2.7.0 through the established 3.0.0-3.0.3 release sequence. This PR follows that repository convention and avoids unrelated lockfile churn; the publish workflow installs successfully with npm ci and publishes the authoritative package.json version.

No release-blocking mismatch found.

[flyingrobots]

Code Lawyer

Semver contract: 3.1.0 is correct for the additive public inspectPrunableObjects() method; no existing API is removed or narrowed.

Artifact contract: package.json and the release changelog both declare 3.1.0; npm pack --dry-run confirms the package identity and expected contents. npm currently reports 3.0.3, so the version is not already published.

Publication contract: after merge, an annotated v3.1.0 tag on merged main triggers .github/workflows/publish.yml, which runs tests, publishes with npm provenance, and creates the GitHub release. No tag will be pushed before this PR is green, reviewed, and merged.

Issue linkage: this publishes #6 and unblocks git-stunts/git-cas#49 and git-stunts/git-cas#55.

No contract ambiguity or release-blocking issue found.

[flyingrobots]

@coderabbitai review

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 4 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5f1280c1-c66d-44a9-a37f-3bb773bb6bb9

📥 Commits

Reviewing files that changed from the base of the PR and between 4a9c8f3 and f3594ef.

📒 Files selected for processing (2)

• CHANGELOG.md
• package.json

---

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