[cknitt]

Stacked on #9001.

The comment's status line showed the head sha and an update time, both already on the last commit's line. The comment now opens with the pull request's changelog entries under their own heading, followed by the Semantic Diff heading:

Changelog

• 🚀 Add @instanceOf("Class") and @typeOf("…") for abstract types …
• 🐛 An untagged variant with both Blob and File cases matches files as File …
• 🏠 Untagged variants recognize stdlib classes only through their @instanceOf annotations …

Semantic Diff

11 commits · Full page

(#8950's entries, rendered locally.)

• The changelog fragments describe the pull request as a whole, as its squash commit will; a commit's Breaking: section describes that commit. The entries are the fragments under changes/ that differ between the merge base and the head (git diff --diff-filter=AM), so a fragment edited later shows in its final form and one added and removed again doesn't show.
• Each bullet is led by its category's emoji as CHANGELOG.md heads the category (scripts/changelog.js's categories), breaking changes first, then in the changelog's order. Fragments are parsed with the changelog's own parseFragment; one that doesn't parse shows its file name with ❔.
• A pull request without fragments reads "No changelog entry." under the Changelog heading.
• When commits have Breaking: sections but no entry is a breaking change, or the other way round, a note under the list says so.
• Fragment Markdown is kept as written, except that @name outside backticks is drawn as code so it notifies no one.

New tests: entries from a range (breaking first, an added-then-removed fragment and README.md left out, an invalid name), and the heading's list, empty state and breaking notes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AzPS5F8RDSGZ6dhfK6NdZp

[github-actions]

Changelog

No changelog entry.

Semantic Diff

2 commits · Full page

List the pull request's changelog entries atop the comment

_{bc14dfc · cknitt + Claude · Oct 23, 2026, 16:33 UTC}

The heading repeated the last commit's sha and a time. The comment now opens with a Changelog section listing the entries the pull request adds, each led by its category's emoji as in the changelog, and noting breaking commits without a breaking entry or the other way round; the Semantic Diff heading follows.

✨ Keep the changelog entries within the comment's budget

_{995e632 · cknitt + Claude · Oct 23, 2026, 16:43 UTC · new}

The budget shortened only commits, so fragments of more than the budget would have pushed the comment past GitHub's limit (Codex). The changelog takes at most a quarter of the budget; entries past it are counted.

[cknitt]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ac564d3d44

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

[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-23T16:46:11.029254Z	995e632	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.

[cknitt]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: 995e632aac

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

[pkg-pr-new]

Open in StackBlitz

rescript

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

@rescript/belt

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

@rescript/darwin-arm64

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

@rescript/linux-arm64

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

@rescript/linux-x64

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

@rescript/runtime

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

@rescript/win32-x64

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

commit: 995e632