Skip to content

chore(release): bump manifest to 0.3.6 for first overlay-build alpha - #1139

Merged
jeonghun-jj-lee merged 1 commit into
mainfrom
bump-v0.3.6-alpha
Sep 14, 2026
Merged

jeonghun-jj-lee merged 1 commit into
mainfrom
bump-v0.3.6-alpha

Conversation

@jeonghun-jj-lee

@jeonghun-jj-lee jeonghun-jj-lee commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

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.50.3.6.

0.3.5 already shipped as a clean release on the pre-absorption fork pipeline. release.yml's version guard requires tag base == manifest version, so cutting the first overlay-build alpha needs the manifest at 0.3.6 to tag v0.3.6-alpha.1.

Why this validates the absorption

A v* tag fires release.yml, whose build-binary job runs build_binary.mjs: materialize (canonical base + overlay) → bun install → the fork's script/build.ts (OPENCODE_CHANNEL=dev), native linux-x64 + cross-compiled linux-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 → watch release.yml → record the run + prerelease on #1118.

Refs #1118 #1091

Summary by CodeRabbit

  • Chores
    • Updated the extension version to 0.3.6.

…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
@coderabbitai

coderabbitai Bot commented Sep 14, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 2bd7e9b1-53c5-496d-908d-756cc199d48e

📥 Commits

Reviewing files that changed from the base of the PR and between 0ebc977 and ab00abb.

📒 Files selected for processing (1)
  • packages/extension/package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The extension package version changes from 0.3.5 to 0.3.6.

Changes

Extension version

Layer / File(s) Summary
Update extension version
packages/extension/package.json
The package metadata changes the extension version from 0.3.5 to 0.3.6.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Suggested reviewers: aarontrowbridge

Merge Risk: ⚪ Minimal · up to ab00a

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)

Check name Status Explanation Resolution
Description check ⚠️ Warning 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 sele… Restructure the description using the repository template. Add a Closes #<issue-number> entry, select the applicable change type, report build and test or typecheck results, and describe any manual testing performed. Keep the existing tec…
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the release-oriented manifest version bump to 0.3.6 and explains its purpose for the first overlay-build alpha.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

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 Closes #&lt;issue-number&gt; entry, select the applicable change type, report build and test or typecheck results, and describe any manual testing performed. Keep the existing technical context in the Description section.

  • Fix all pre-merge checks with AI
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bump-v0.3.6-alpha

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@jeonghun-jj-lee
jeonghun-jj-lee merged commit f3ab4a1 into main Sep 14, 2026
11 checks passed
@jeonghun-jj-lee
jeonghun-jj-lee deleted the bump-v0.3.6-alpha branch September 14, 2026 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant