Skip to content

chore(release): prepare plugin-inspector 0.3.27 - #95

Merged
vincentkoc merged 1 commit into
mainfrom
release/plugin-inspector-0.3.27
Oct 1, 2026
Merged

vincentkoc merged 1 commit into
mainfrom
release/plugin-inspector-0.3.27

Conversation

@vincentkoc

@vincentkoc vincentkoc commented Oct 1, 2026 •

Copy link
Copy Markdown
Member

What Problem This Solves

Prepares the merged plugin-inspector fixes and resource-profile API for the 0.3.27 release.

User Impact

User impact: operators receive the current path-safety, generated-workflow, SDK capture, and resource-measurement improvements in the published package.

Why This Change Was Made

Advances the package and lockfile versions to 0.3.27 and moves the existing Unreleased notes into the October 1, 2026 release section. The eslint-scope dependency remains on 8.4.0.

Evidence

  • Exact main 19f481f19f06746f2ccc14d2e03e6a52db74ce14: hosted Node 22 check and CodeQL green.
  • Exact candidate 7c44cdec59fd3879c751a2b7e1874c8051bf2259: hosted Node 22 and CodeQL green.
  • Node 24.21.0: all 571 tests passed.
  • Package-content validation passed with 61 entries.
  • npm pack --dry-run produced @openclaw/plugin-inspector@0.3.27 with the expected exports and no test, script, or workflow files.
  • Crabpot candidate follow-through: chore: adopt plugin-inspector 0.3.27 crabpot#407
  • Crabpot source-mode smoke against this exact candidate: 59 fixtures, zero breakages, 59 logs.
  • Crabpot source/package pin guards: 8 tests passed.
  • Crabpot follow-through check passed the candidate source ref and public-API migration checks; package mode remains on published 0.3.26 until publication.
  • npm currently publishes 0.3.26; no 0.3.27 tag, GitHub release, or npm package exists.

@vincentkoc vincentkoc self-assigned this Oct 1, 2026
@clawsweeper

clawsweeper Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Oct 1, 2026
@clawsweeper

clawsweeper Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Codex review: needs changes before merge. Reviewed October 1, 2026, 4:42 AM ET / 08:42 UTC (Revision 2).

ClawSweeper review

What this changes

This PR sets the package and lockfile versions to 0.3.27 and places the existing unreleased notes under an October 1 release heading.

Merge readiness

⛔ Needs changes before merge - 1 item remains

The previous staged-release blockers are addressed. The release preparation remains necessary, and no introduced correctness or supply-chain defect was found.

Priority: P3
Reviewed head: 7c44cdec59fd3879c751a2b7e1874c8051bf2259

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) A focused, consistent release patch with the previous follow-through request addressed.
Proof confidence 🌊 off-meta tidepool Not applicable: The MEMBER-authored metadata PR is exempt from contributor runtime proof; recorded package validation and Crabpot source smoke exercise the exact candidate. No stored-data contract changes.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Verification

Check Result Evidence
Real behavior Not applicable Not applicable: The MEMBER-authored metadata PR is exempt from contributor runtime proof; recorded package validation and Crabpot source smoke exercise the exact candidate. No stored-data contract changes.
Evidence reviewed 7 items Exact introduced release diff: The pinned delta changes only the changelog heading and three package-version values; dependencies, exports, runtime code, and publishing workflow remain unchanged. The verified test-merge result has the same three-file scope.
Applicable release policy and dependency signal: The full root AGENTS.md requires Crabpot follow-through for release metadata changes. README.md explicitly requires candidate source smoke before tagging and defers the package-pin update until after npm publication.
Staged package pin is supported: The follow-through checker treats an older package pin as manual before publication and fails it only in published mode; regression tests explicitly cover this distinction.
Findings None None.
Security None None.

How this fits together

Plugin Inspector checks OpenClaw plugin compatibility and produces reports consumed by operators and Crabpot. Release metadata identifies the package published through the existing tag-triggered workflow.

flowchart LR
  A[Merged Inspector improvements] --> B[Version and release notes]
  B --> C[Candidate package checks]
  C --> D[Crabpot source smoke]
  D --> E[Owner-approved release]
  E --> F[Published npm package]
  F --> G[Crabpot package smoke]
Loading

Before merge

  • Complete next step (P2) - Mark this draft ready for review before merge.
Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Use the existing staged release process, then advance and validate Crabpot's published-package pin after owner-approved publication.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this PR prepares release metadata rather than repairing a reported runtime failure.

Is this the best way to solve the issue?

Yes: the synchronized version bump and versioned changelog follow the documented release process, including the staged Crabpot package update.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 19f481f19f06.

Labels

Label changes:

No label changes.

Label justifications:

  • P3: This is a small release-metadata preparation with no introduced runtime behavior change.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The MEMBER-authored metadata PR is exempt from contributor runtime proof; recorded package validation and Crabpot source smoke exercise the exact candidate. No stored-data contract changes.

Evidence

What I checked:

  • Exact introduced release diff: The pinned delta changes only the changelog heading and three package-version values; dependencies, exports, runtime code, and publishing workflow remain unchanged. The verified test-merge result has the same three-file scope. (package.json:3, 7c44cdec59fd)
  • Applicable release policy and dependency signal: The full root AGENTS.md requires Crabpot follow-through for release metadata changes. README.md explicitly requires candidate source smoke before tagging and defers the package-pin update until after npm publication. (README.md:675, 7c44cdec59fd)
  • Staged package pin is supported: The follow-through checker treats an older package pin as manual before publication and fails it only in published mode; regression tests explicitly cover this distinction. (scripts/check-crabpot-followthrough.mjs:58, 7c44cdec59fd)
  • Candidate follow-through verified: chore: adopt plugin-inspector 0.3.27 crabpot#407 is an open staged follow-through PR. Its patch pins source mode to the exact Inspector candidate, updates the guard and operations documentation, and intentionally preserves package mode at 0.3.26. Its body records 59 source-smoke fixtures, zero breakages, 59 logs, eight passing pin guards, and the post-publication update. (scripts/plugin-inspector-source.mjs:8, c2c4620a5283)
  • Re-review disposition: The captured maintainer comment chore(release): prepare plugin-inspector 0.3.27 #95 (comment) supplies the exact-candidate smoke results and staged follow-through requested by the previous review. No prior code findings were recorded. (7c44cdec59fd)
  • Still necessary on main: Pinned main still declares 0.3.26; the latest GitHub release is v0.3.26, published September 20. The requested 0.3.27 preparation is therefore not already implemented on the reviewed default branch. (package.json:3, 19f481f19f06)

Likely related people:

  • vincentkoc: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
  • RomneyDa: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (1 earlier review cycle)
  • reviewed 2026-10-01T08:34:12.678Z sha 7c44cde :: blocked before merge. :: none

@vincentkoc

Copy link
Copy Markdown
Member Author

@clawsweeper re-review

The two staged-release items are now addressed:

  • Crabpot candidate follow-through PR: chore: adopt plugin-inspector 0.3.27 crabpot#407
  • exact candidate source pin: 7c44cdec59fd3879c751a2b7e1874c8051bf2259
  • source-mode smoke: 59 fixtures, zero breakages, 59 logs
  • source/package pin guards: 8 tests passed
  • package mode intentionally remains on published 0.3.26 until 0.3.27 is published

The release PR body now records this evidence and the post-publication package-pin step.

@clawsweeper

clawsweeper Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

🦞👀
Exact review queued.

Re-review progress:

@vincentkoc
vincentkoc marked this pull request as ready for review October 1, 2026 08:43
@vincentkoc
vincentkoc requested a review from a team as a code owner October 1, 2026 08:43
@vincentkoc
vincentkoc merged commit b8321a8 into main Oct 1, 2026
6 of 7 checks passed
@vincentkoc
vincentkoc deleted the release/plugin-inspector-0.3.27 branch October 1, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant