Skip to content

chore(release): bump boxlite-agent-tooling to 0.1.31 - #261

Merged
DorianZheng merged 1 commit into
mainfrom
release-0-1-31
Oct 23, 2026
Merged

DorianZheng merged 1 commit into
mainfrom
release-0-1-31

Conversation

@DorianZheng

Copy link
Copy Markdown
Member

TL;DR

Plugin version 0.1.31 ships the research gate, the Stop gate exec and the TL;DR first-block rule, so hosts can tell them apart from cached 0.1.30 resources.

Design doc: #256

Documentation: CONTRIBUTING.md, Research gate and TL;DR rollout

How it works

Everything since #251 shipped under 0.1.30, and the commit/push gate spots a stale session plugin only by version. This PR:

  • Sets all seven version fields (three plugin manifests, two fields in each of two marketplaces) to 0.1.31.
  • Adds a rollout note: research review before the first code edit; one editor edit before the next commit or push for code from any 0.1.30 build; the TL;DR first-block rule; reload sessions.

Verification

Check Result
make test:parity 208 of 208, every version 0.1.31
make test:architecture 139 of 139
make test:writing test:guidance-check exit 0, no findings

The research gate (#254), the auditor-control fix (#250), the verdict
check exec (#258) and the TL;DR first-block rule (#260) all shipped
under 0.1.30. The commit/push gate detects a stale session plugin only
by version, so loaded 0.1.30 auditors would reject the newer tasks
instead of asking for a reload.

All seven version fields move to 0.1.31, and CONTRIBUTING gains a
rollout note: research is reviewed before the first edit, code from any
0.1.30 build gets that review before its next commit or push, TL;DR
summaries must open with a paragraph, and sessions must reload.

Rejected: keeping 0.1.30, whose equal versions skip the reload check.

Fixes #256
@coderabbitai

coderabbitai Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: QUIET
  • Plan: Advanced
  • Run ID: d18c4b94-dcbc-4b94-bfd0-39433a8891d8
📥 Commits

Reviewing files that changed from the base of the PR and between 2a6b01d and ad3a635.

📒 Files selected for processing: 6
  • .claude-plugin/marketplace.json
  • .github/plugin/marketplace.json
  • plugins/boxlite-agent-tooling/.claude-plugin/plugin.json
  • plugins/boxlite-agent-tooling/.codex-plugin/plugin.json
  • plugins/boxlite-agent-tooling/CONTRIBUTING.md
  • plugins/boxlite-agent-tooling/plugin.json
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

@github-actions

Copy link
Copy Markdown
Contributor

TL;DR

The PR author must acknowledge the current diff and description before requesting review.

Author review acknowledgment

Awaiting the PR author's acknowledgment.

@DorianZheng: read the current diff and description, then check:

Apply boxlite-writing. Does How it works explain the diff's mechanism or rationale?

Use the form best suited to the change. Check drafts too, and repeat this review
after description edits. Post this as a new PR comment:

/reviewed ad3a635b5edb5d7506ecc68aa757f2feef60549e

Unacknowledged PRs are converted to draft. After this check passes, click Ready for review when you want reviews.
Only a new, unedited comment from the PR author counts. A new commit requires a new acknowledgment.
This records the author's acknowledgment of the commit, not an automated judgment of the description; maintainer approval is separate.

@DorianZheng
DorianZheng marked this pull request as ready for review October 23, 2026 11:28
@DorianZheng
DorianZheng merged commit fd97a29 into main Oct 23, 2026
7 of 8 checks passed
@DorianZheng
DorianZheng deleted the release-0-1-31 branch October 23, 2026 11:28
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