chore(release): bump manifest to 0.3.6 for first overlay-build alpha - #1139
Conversation
…ild alpha 0.3.5 shipped as a clean release on the pre-absorption fork pipeline. This bump lets v0.3.6-alpha.1 pass release.yml's version guard and cut the first alpha whose binary is built end-to-end from the absorbed overlay tree (build_binary.mjs: materialize -> bun -> script/build.ts), validating the #1091 pipeline. Prerequisite for unblocking #1118. Refs #1118 #1091
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe extension package version changes from ChangesExtension version
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to The extension version bump is limited in scope and aligns with the supplied release workflow contract, so it is mergeable. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description explains the change, purpose, release process, and related issues, but it does not follow the required template. It omits the required Related Issue closure syntax, Type of Change selection, Verification status, and Manual Testing Notes. Resolution Restructure the description using the repository template. Add a
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Source
Prerequisite for unblocking #1118 (fork-vocabulary sweep), which is gated on "an alpha validated the overlay-build binary end-to-end." No such alpha exists yet — the last one (
v0.3.5-alpha.8, 2026-09-11) predates the absorbed pipeline by 3 days.What
One-line bump: extension manifest
0.3.5→0.3.6.0.3.5already shipped as a clean release on the pre-absorption fork pipeline.release.yml's version guard requirestag base == manifest version, so cutting the first overlay-build alpha needs the manifest at0.3.6to tagv0.3.6-alpha.1.Why this validates the absorption
A
v*tag firesrelease.yml, whosebuild-binaryjob runsbuild_binary.mjs: materialize (canonical base + overlay) →bun install→ the fork'sscript/build.ts(OPENCODE_CHANNEL=dev), nativelinux-x64+ cross-compiledlinux-arm64/darwin-arm64. No fork download — this is exactly the end-to-end path #1118 waits on. Alpha ⇒publishable=false⇒ GitHub prerelease only, no Marketplace.Plan
Merge → tag the merge commit
v0.3.6-alpha.1→ watchrelease.yml→ record the run + prerelease on #1118.Refs #1118 #1091
Summary by CodeRabbit