[fhammerschmidt]

API documentation checks and publication currently follow the website’s default branch. With stable docs now on v12, compiler master (v13) can otherwise publish prerelease APIs into stable documentation.

Derive the target as v${major} from the compiler package version and use it for CI and release checkout/push. This keeps API routing independent of website promotion and compiler maintenance branch cuts. The shared playground refresh hook continues to target the default website.

Related to #8753.

Next steps

1. Merge this PR, then separately pin maintenance/12.x API publication to docs v12.
2. Prepare docs v13 with its matching compiler/example formatting and deployment routing; keep v12 as the public default until release.
3. Publish compiler v13 stable, then promote docs v13 to default, align Cloudflare’s production branch and playground hook, and deploy. Cut maintenance/13.x before compiler master advances to the next major.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-21T17:32:41.497350Z	40a05a7	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.29%. Comparing base (c9a267c) to head (f3eb117).
⚠️ Report is 6 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8945      +/-   ##
==========================================
+ Coverage   81.27%   81.29%   +0.01%     
==========================================
  Files         456      456              
  Lines       63828    63836       +8     
==========================================
+ Hits        51875    51893      +18     
+ Misses      11953    11943      -10     

see 5 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Changelog

• 🏠 Route API documentation checks and publication to the website branch matching
  the compiler major (v12, v13, and later), keeping the target unchanged when
  a release becomes current stable or moves to a maintenance branch.

Semantic Diff

4 commits · Full page

Route API docs to the website branch matching the compiler major

_{0c5afa5 · fhammerschmidt · Oct 21, 2026, 16:34 UTC}

Why

Following the website default branch lets v13 compiler prereleases update stable v12 API docs. The target must follow the compiler package version through website promotions and maintenance branch cuts.

Select v<major> for API checks and publication, push to that branch explicitly, and cover maintenance branches in CI. Test release promotion and branch cuts without changing the API documentation destination.

Run release planning from Windows script paths

_{40a05a7 · fhammerschmidt · Oct 21, 2026, 16:51 UTC}

Why

The API routing CLI tests exposed an entry-point check that compares a file URL to a Windows path prefixed with file://. It skips main on Windows and exits successfully without writing the workflow outputs.

Compare resolved filesystem paths, using the same check as changelog.js. The existing CLI output tests cover the failure on Windows CI.

✨ Remove the deleted release branch from push CI

_{849306e · fhammerschmidt + Christoph Knittel · Oct 22, 2026, 15:43 UTC · new}

The review noted that 11.0_release no longer exists. Keep CI on master and maintenance branches for push events.

✨ Remove the deleted release branch from pull request CI

_{e533ad4 · fhammerschmidt + Christoph Knittel · Oct 22, 2026, 15:43 UTC · new}

The review noted that 11.0_release no longer exists. Keep CI on master and maintenance branches for pull request events.

[pkg-pr-new]

Open in StackBlitz

rescript

npm i https://pkg.pr.new/rescript@8945

@rescript/belt

npm i https://pkg.pr.new/@rescript/belt@8945

@rescript/darwin-arm64

npm i https://pkg.pr.new/@rescript/darwin-arm64@8945

@rescript/linux-arm64

npm i https://pkg.pr.new/@rescript/linux-arm64@8945

@rescript/linux-x64

npm i https://pkg.pr.new/@rescript/linux-x64@8945

@rescript/runtime

npm i https://pkg.pr.new/@rescript/runtime@8945

@rescript/win32-x64

npm i https://pkg.pr.new/@rescript/win32-x64@8945

commit: f3eb117

[github-actions]

Developer playground preview: https://rescript-lang.github.io/rescript/dev-playground/?version=pr-8945

[cknitt]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: 40a05a71c7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".