chore(release): prepare 0.40.0-beta.4 - #628
Merged
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (15)
📝 WalkthroughWalkthroughThis release-preparation change promotes retrieval regression ChangesBeta.4 release preparation
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
mohanagy
commented
Jul 30, 2026
mohanagy
left a comment
mohanagy
left a comment
Owner
Author
There was a problem hiding this comment.
Independent exact-head release review — PASS, no blocker.
Reviewed base b6562b715133304bd46e537b6f39008bc1e02095, head 8d30d9e1ee22814c1876ef525a31b3eccdcf11ca, tree f51d6e75e3b806dec6caf9ff0be43fc2ab5713fc.
Findings:
- Scope is release-only: 15 metadata, documentation, governance, SBOM, workflow, and test paths; no
src/**or evaluation-tool change. - After removing only the root version fields,
package.jsonandpackage-lock.jsonare identical to the protected base. Dependencies, scripts, public surfaces, and semantics are unchanged. - The release workflow diff is limited to the beta.4 version authorization plus expected shasum/integrity. It retains exact protected-
nexttip checks, exact remote-tag checks, OIDC provenance, npmnext, immutablelatest=0.32.0, signature/provenance verification, and an exact-commit GitHub prerelease after npm verification. It does not publish MCP Registry metadata or targetmain. - A fresh archive of this exact tree rebuilt with npm 12.0.1 reproduced all recorded receipts: 102 files, 159,937 packed bytes, 639,875 unpacked bytes, shasum
c5250a0d308b3d6df374851154ddb393a678a992, integritysha512-772P+n4Cx55nqC+CAx8A1aTJ2rY4yk1hUH45lAlxNMMw4YRj8hhswgDiCwczS5hx1S3a+Z+KUv2jma/zWjQZ6w==, and tarball SHA-2568bd8d501b8cd3546e16a5a1ddac1f7649434e685517e1171fbd5897515e76e6b. - #625 governance completion matches live #626 receipts: final reviewed tree was preserved by protected squash merge
b6562b715133304bd46e537b6f39008bc1e02095; its CI/review/CodeRabbit/zero-thread claims are consistent. - Release hygiene, MCP Registry schema validation, typecheck, and 29 focused release/governance tests pass on the exact candidate. Tests cover version pins, artifact hashes, protected-next publication constraints, unchanged latest, GitHub prerelease behavior, completed #625 receipts, current release-preparation state, and stale-governance rejection.
- CodeRabbit reported no actionable findings on this exact diff and its required status is successful. Its PR-description template warning is non-code and non-blocking. Review threads are currently zero.
This review is not a substitute for the remaining merge gates: all six required CI jobs must be green on this unchanged head and zero unresolved threads must remain at merge time.
Owner
Author
|
Final merge-gate receipt for exact candidate head
The candidate may now be squash-merged into protected |
Owner
Author
|
Publication completion receipt for
No MCP Registry publication was dispatched, no stable/npm |
This was referenced Aug 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #627.
Prepares
@lubab/madar@0.40.0-beta.4from protectednextfor publication under the npmnextdist-tag and a matching GitHub prerelease.Scope:
Exact candidate:
b6562b715133304bd46e537b6f39008bc1e020958d30d9e1ee22814c1876ef525a31b3eccdcf11caf51d6e75e3b806dec6caf9ff0be43fc2ab5713fcc5250a0d308b3d6df374851154ddb393a678a992sha512-772P+n4Cx55nqC+CAx8A1aTJ2rY4yk1hUH45lAlxNMMw4YRj8hhswgDiCwczS5hx1S3a+Z+KUv2jma/zWjQZ6w==8bd8d501b8cd3546e16a5a1ddac1f7649434e685517e1171fbd5897515e76e6bLocal gates passed under workflow-equivalent Node 22/npm 12: release hygiene, Registry metadata validation, typecheck, 684/684 tests with coverage, production/evaluation builds, baseline, packed retrieval parity, dependency audit, registry signatures, Core Reset isolation, dry-run pack, and exact reproducible pack. Independent pre-publication review found no blocker.
Merge gate: exact head must retain all six required CI checks green, independent review must find no blocker, CodeRabbit must be stated honestly, and zero unresolved review threads must remain. This PR does not publish npm, create a GitHub Release, publish MCP Registry metadata, tag, target
main, or changelatest.Summary by CodeRabbit
Release
0.40.0-beta.4.Bug Fixes
Documentation