[cknitt]

Two leftovers in CI and the test script no longer do anything useful.

• The syntax benchmark step in ci.yml wrote its output to a file nothing read since benchmark tracking was disabled, followed by the commented-out benchmark-action steps. Both are gone, along with the benchmarks matrix flag only that step used, saving about 30 s on the linux-arm64 job. The syntax_benchmarks executable and make bench stay.
• scripts/test.js skipped the docstring tests on macOS 13 to work around hangs on that runner. CI runs on macos-26 and the Makefile refuses Intel Macs, so the docstring tests now always run.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Kbf3gKyiYMf54wPRxFdUWe

[github-actions]

Changelog

🏠 Internal

• Remove the unused syntax benchmark CI step and the macOS 13 docstring test workaround.

Semantic Diff

2 commits · Full page

Drop the syntax benchmark step from CI

_{9f05294 · cknitt + Claude · Oct 31, 2026, 06:05 UTC}

The step wrote its output to a file nothing read since benchmark tracking was disabled, so it only cost about 30 seconds per run.

Always run the docstring tests on macOS

_{6e40255 · cknitt + Claude · Oct 31, 2026, 06:05 UTC}

The skip for macOS 13 worked around hangs on a runner CI no longer uses: CI runs on macos-26 and the Makefile refuses Intel Macs.

[pkg-pr-new]

Open in StackBlitz

rescript

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

@rescript/belt

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

@rescript/darwin-arm64

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

@rescript/linux-arm64

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

@rescript/linux-x64

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

@rescript/runtime

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

@rescript/win32-x64

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

commit: 6e40255

[github-actions]

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

[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-31T07:34:30.843059Z	6e40255	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. What shall we delve into next?

Reviewed commit: 6e40255016

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