Repository navigation
fix(release): qualify and protect babelfish 0.1.1 publication - #47
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 maintainer review before merge. Reviewed October 1, 2026, 7:17 AM ET / 11:17 UTC (Revision 2). ClawSweeper reviewWhat this changesThe branch qualifies Babelfish 0.1.1 packages in an isolated consumer, aligns MCP version identities, and adds signed-tag publication with independent registry verification. Merge readiness✅ Ready for maintainer review The prior blockers are repaired, and no remaining actionable defect was found. The release preparation remains necessary because current main lacks the introduced publication workflow and installed-package validation. Priority: P2 Review scores
Verification
How this fits togetherBabelfish translates Hermes, Claude Code, and Codex plugins for OpenClaw. Its release tooling turns built package contents into a tested npm archive, then verifies publication before promoting the GitHub release. flowchart TD
A[Signed protected tag] --> B[Validate source]
B --> C[Build and test package]
C --> D[Retain immutable archive]
D --> E[Protected npm publisher]
E --> F[Registry and consumer verification]
F --> G[GitHub release promotion]
Before mergeNone. Agent review detailsSecurityNone. Review metrics
Technical reviewBest possible solution: Retain the isolated publication and verification design, then follow the documented protected-tag and npm preflight procedure for the first release. Do we have a high-confidence way to reproduce the issue? Not applicable to the release preparation as a whole; source inspection and the exact GitHub comparison establish that both previously reported helper failures are repaired. Is this the best way to solve the issue? Yes. Validating retained package bytes in a fresh consumer and separating publication from verification is a focused improvement over main's dry-run and checkout-import checks. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against dee86b098869. LabelsLabel 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)
|
Summary
dee86b098869f8b3db890ae8e638d5ba23c97ef2.Compatibility
contents:readandid-token:write, usesstable-release, and has no checkout/install/cache/lifecycle. Exact E404 admits one publish invocation; existing/uncertain writes reconcile retained bytes and never blindly republish. Mandatory verifier checks cryptographic signatures/provenance and exact subject/source/workflow/tag/repository/run/publishing-attempt identities before promotion.Verification
npm run check: 250 passed across 14 files, build passed.a2349d9521f7af1ec4246e2078f30e758ec7ff818cd279f13ff15b247954f050.actionlint, embedded publisher Python syntax, Node script syntax, and diff whitespace checks passed.Current release-prep head:
220c5834bab649bb1dee0a4dfb5a578c4cf59673. Scoped review repairs cover failed-job retry admission, offline registry packument qualification, complete npm PURL encoding, digit-bearing artifact outputs, and canonical repository metadata URLs. Focused regressions cover both deterministic ClawSweeper findings. No dependencies or public runtime contracts changed.This is the release preparation PR only. Contributor PRs are settled and are not reopened or rerun.