Repository navigation
chore(release): prepare plugin-inspector 0.3.27 - #95
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
Codex review: needs changes before merge. Reviewed October 1, 2026, 4:42 AM ET / 08:42 UTC (Revision 2). ClawSweeper reviewWhat this changesThis 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 Review scores
Verification
How this fits togetherPlugin 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]
Before merge
Agent review detailsSecurityNone. Review metricsNone. Technical reviewBest 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. LabelsLabel changes: No label changes. Label justifications:
EvidenceWhat I checked:
Likely related people:
Rating scale
Overall follows the weaker of proof and patch quality. Workflow
HistoryReview history (1 earlier review cycle)
|
|
@clawsweeper re-review The two staged-release items are now addressed:
The release PR body now records this evidence and the post-publication package-pin step. |
|
🦞👀 Re-review progress:
|
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-scopedependency remains on 8.4.0.Evidence
19f481f19f06746f2ccc14d2e03e6a52db74ce14: hosted Node 22 check and CodeQL green.7c44cdec59fd3879c751a2b7e1874c8051bf2259: hosted Node 22 and CodeQL green.npm pack --dry-runproduced@openclaw/plugin-inspector@0.3.27with the expected exports and no test, script, or workflow files.