Skip to content

chore(release): prepare plugin-inspector 0.3.26 - #88

Merged
RomneyDa merged 1 commit into
mainfrom
release/inspector-0.3.26
Sep 20, 2026
Merged

RomneyDa merged 1 commit into
mainfrom
release/inspector-0.3.26

Conversation

@RomneyDa

Copy link
Copy Markdown
Member

What Problem This Solves

Prepares the reviewed Plugin Inspector fixes since v0.3.25 for the v0.3.26 release.

Why This Change Was Made

Updates only the package version, matching lockfile fields, and dated changelog. Runtime code, dependencies, and the tag-triggered trusted-publishing workflow are unchanged by this PR.

Evidence

  • Candidate: 7253a17fde1a31595435b4d4c4e23ecb64e4f161.
  • npm run release:local: 545 tests passed; package contents passed with 60 entries.
  • Packed candidate installed in isolation: CLI help passed and all 19 public exports loaded.
  • Candidate tarball SHA-256: ccabd353e00150ba29a0f8877e21fc78d6ee6ef44428dae8c5d07f1a1f854725.
  • Crabpot source-mode smoke: 59 fixtures, zero breakages.
  • Crabpot installed-candidate smoke: 59 fixtures, zero breakages.
  • Pre-publication follow-through check passes the exact candidate source ref and public-API migration gate; the package pin intentionally remains v0.3.25 until trusted publication completes.

Follow-through

Crabpot source pin is staged separately. After this PR lands, it will be repinned to the landed commit before tagging. After trusted publication, Crabpot and OpenClaw package pins will advance to v0.3.26.

@RomneyDa
RomneyDa requested a review from a team as a code owner September 20, 2026 18:01
@clawsweeper

clawsweeper Bot commented Sep 20, 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 Sep 20, 2026
@clawsweeper

clawsweeper Bot commented Sep 20, 2026

Copy link
Copy Markdown

Codex review: needs maintainer review before merge. Reviewed September 20, 2026, 2:03 PM ET / 18:03 UTC.

ClawSweeper review

What this changes

Updates the package and lockfile versions to 0.3.26 and moves the existing unreleased notes into a dated release section.

Merge readiness

✅ Ready for maintainer review

This release preparation remains necessary: current main and the latest release are still 0.3.25. The metadata changes are consistent, and the linked Crabpot follow-through matches the documented release sequence. No blocking defect was found.

Priority: P3
Reviewed head: 7253a17fde1a31595435b4d4c4e23ecb64e4f161

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) A focused, consistent release-preparation patch with relevant reported package validation and verified companion follow-through.
Proof confidence 🐚 platinum hermit (4/6) Not applicable: The MEMBER-authored metadata-only PR is exempt from the external-contributor proof gate; its reported isolated package installation, export loading, and Crabpot smoke runs directly support release preparation.
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-only PR is exempt from the external-contributor proof gate; its reported isolated package installation, export loading, and Crabpot smoke runs directly support release preparation.
Evidence reviewed 6 items Pinned release-only delta: The complete introduced diff changes three version fields to 0.3.26, adds the dated changelog heading, and removes one blank line. It changes no runtime code, dependencies, exports, lifecycle hooks, or publishing workflow.
Current-main and release comparison: The inspected package.json on fetched main still declares 0.3.25. GitHub's latest-release endpoint reports v0.3.25, published September 9, 2026; the proposed release preparation is not already present.
Applicable consumer follow-through policy: AGENTS.md requires Crabpot follow-through for version changes. The release documentation explicitly places source repinning before tagging and the published package-pin update after npm publication. The checklist and its tests preserve that distinction.
Findings None None.
Security None None.

How this fits together

Plugin Inspector checks OpenClaw plugin compatibility and supplies reports to consumers such as Crabpot. Its release metadata determines the npm package version and the notes published by the tag-triggered release workflow.

flowchart LR
 A[Reviewed fixes] --> B[Version and changelog]
 B --> C[Package verification]
 C --> D[Release tag]
 D --> E[npm and GitHub release]
 E --> F[Crabpot package adoption]
Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Land the focused release metadata, then complete the documented Crabpot repinning and published-package checks through the companion adoption PR.

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

Not applicable: this PR prepares a release rather than reporting a runtime defect; the complete version and changelog delta was inspected.

Is this the best way to solve the issue?

Yes. The minimal metadata update follows the existing release contract, including deferring Crabpot's npm pin until the package is published.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 1dc371a1badc.

Labels

Label changes:

  • add P3: This is a focused release-metadata update with no introduced runtime behavior change.
  • add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The MEMBER-authored metadata-only PR is exempt from the external-contributor proof gate; its reported isolated package installation, export loading, and Crabpot smoke runs directly support release preparation.

Label justifications:

  • P3: This is a focused release-metadata update with no introduced runtime behavior change.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit 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-only PR is exempt from the external-contributor proof gate; its reported isolated package installation, export loading, and Crabpot smoke runs directly support release preparation.

Evidence

What I checked:

  • Pinned release-only delta: The complete introduced diff changes three version fields to 0.3.26, adds the dated changelog heading, and removes one blank line. It changes no runtime code, dependencies, exports, lifecycle hooks, or publishing workflow. (package.json:3, 7253a17fde1a)
  • Current-main and release comparison: The inspected package.json on fetched main still declares 0.3.25. GitHub's latest-release endpoint reports v0.3.25, published September 9, 2026; the proposed release preparation is not already present. (package.json:3, 1dc371a1badc)
  • Applicable consumer follow-through policy: AGENTS.md requires Crabpot follow-through for version changes. The release documentation explicitly places source repinning before tagging and the published package-pin update after npm publication. The checklist and its tests preserve that distinction. (docs/releasing.md:95, 7253a17fde1a)
  • Companion adoption verified: chore: adopt plugin-inspector 0.3.26 crabpot#317 is open. Its inspected patch pins pluginInspectorRef to the exact Inspector candidate and updates the corresponding guard. Its body reports source-mode and installed-candidate smoke results of 59 fixtures with zero breakages, and explicitly tracks the landed-SHA and post-publication package-pin updates. (scripts/plugin-inspector-source.mjs:7, 608d050169f6)
  • Candidate validation evidence: The supplied PR body identifies candidate 7253a17 and reports 545 passing tests, 60 package entries, an isolated installed-package CLI check, all 19 exports loading, and both Crabpot smoke modes passing. These are contributor-reported results; this read-only review did not execute tests or package commands. (7253a17fde1a)
  • Release-area routing history: Main-branch file history records Vincent Koc's work on release planning, Crabpot follow-through, and the previous release preparation. GitHub commit metadata maps the release-plan commit to vincentkoc. Exact historical source-line verification was unavailable because a required historical blob could not be read, so no introduction claim is made. (docs/releasing.md, 527b2eae828e)

Likely related people:

  • vincentkoc: 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.

@RomneyDa
RomneyDa merged commit 6169338 into main Sep 20, 2026
9 checks passed
@RomneyDa
RomneyDa deleted the release/inspector-0.3.26 branch September 20, 2026 18:04
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