[cknitt]

Fixes #8971.

Updates the unreleased fragments that later pull requests in the same cycle superseded, so yarn changelog:release no longer publishes them as written:

• semantic-diff-fragments.internal.md (Read the semantic diff's changelog from changes/ fragments #8881) is removed: Semantic diff: write and draw changes as semantic objects #8908 took out the fragment reading it describes.
• linear-char-range-patterns.fix.md (Compile character range patterns in linear time #8868) no longer promises faster switches over many constants, since Remove the hashing fast paths from pattern matching #8900 removed those fast paths (remove-match-fast-paths.internal.md).
• playground-api-v8-compatibility.fix.md (Keep optimized Lambda output compatible with playground API v8 #8930) is removed: the API v9 bump it reverts (Developer playground: compare Lambda before and after optimization #8636) is unreleased too, so no release had the regression.
• watch-rebuild-recovery.fix.md (Keep watch alive after rebuild errors #8641) and rewatch-overlapping-unwatch.fix.md (Fix rewatch losing watches when an overlapping source folder is removed #8839) now start with rescript-rust:, because both changed only the Rust build system. rescript's watcher recovers only on configuration changes, as rewatch-ocaml/README.md says.
• ocaml-rewatch-strict-config.breaking.md gains the other user-visible differences that rewatch-ocaml/README.md lists: the --filter regular expression subset, a failing --after-build failing the build (with no interactive terminal on Unix), format -v/compiler-args -v logging to stderr, and no OpenTelemetry export.

This PR changes only release notes, so it adds no fragment of its own and needs the changelog:skip label.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Xk6AeCYpCK4SZRtHYKHGoe

[github-actions]

Semantic Diff

1 commit · Full page

Update unreleased changelog fragments that later changes superseded

_{2559c48 · Christoph Knittel with Claude Opus 5.5 · Oct 23, 2026}

Several fragments no longer described the next release: the semantic diff no longer reads fragments (#8908), switches over many constants are no longer faster (#8900), the playground API v9 bump and its revert are both unreleased, two watcher fixes apply only to rescript-rust, and the breaking changes of the OCaml build system missed some user-visible differences listed in rewatch-ocaml/README.md.

[pkg-pr-new]

Open in StackBlitz

rescript

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

@rescript/belt

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

@rescript/darwin-arm64

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

@rescript/linux-arm64

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

@rescript/linux-x64

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

@rescript/runtime

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

@rescript/win32-x64

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

commit: 2559c48

[github-actions]

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

[cknitt]

@codex review

[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-23T09:27:09.442471Z	2559c48	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.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: 2559c48efb

ℹ️ 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".