Derive changelog PR links from the squash commit

[cknitt]

Changelog fragments no longer contain PR links. A fragment is just the entry:

- Recover blocked dependents after a failed build.

yarn changelog:release adds each link itself, from the squash commit that merged the fragment (… (#8667)). New PRs no longer need the draft with the pull/XXXX placeholder, and the amend once the number is known.

• scripts/changelog.js:
  • A bullet may end without a link. A bullet that does end with links keeps them as written, e.g. for an entry spanning several PRs.
  • At release, each linkless bullet gets the link of the PR whose commit added the fragment. Entries are still ordered newest PR first. In a preview, fragments not merged yet come first.
  • The release refuses, naming the fragment, if that commit's subject has no (#N). It writes nothing in that case.
  • The check that runs on each push to master traces every linkless fragment to its PR, so a merge without (#N) fails right after it lands rather than at release time.
• changes/README.md and AGENTS.md: the placeholder steps are replaced by the squash-merge rule.

Repository settings

This relies on PRs being squash-merged with the (#N) GitHub adds to the title. The repository now allows only squash merges, titled with the PR title and (#N) ("Default to pull request title and commit details"). Since v13.0.0-alpha.6, 128 of 131 commits on master were squash merges. The other 3 were rebase merges (#8870, #8669) and carry no PR number.

Checked against history

I stripped the links from every fragment on master and derived them again. 46 of 47 fragments got exactly their original links back, and the release produces an identical CHANGELOG.md. The one miss is commit-records.internal.md, from the rebase-merged #8870; the release refuses it as described above. This PR's own fragment has no link, so it resolves once this PR is squash-merged.

Tests

scripts/changelog.test.js:

• linking per bullet, including continuation lines and fragments mixing linked and linkless bullets;
• a release that refuses without changing any files, then succeeds;
• ordering of linkless fragments in previews;
• the lookup in a throwaway repository: a squash subject, a subject without a number, and a later edit by another PR, which does not change who added the fragment.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NP47qMfjMbjUTKZDsLthDo

[pkg-pr-new]

Open in StackBlitz

rescript

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

@rescript/belt

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

@rescript/darwin-arm64

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

@rescript/darwin-x64

npm i https://pkg.pr.new/@rescript/darwin-x64@8888

@rescript/linux-arm64

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

@rescript/linux-x64

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

@rescript/runtime

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

@rescript/win32-x64

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

commit: 73d89ca

[github-actions]

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

[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-18T06:45:13.973766Z	73d89ca	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

Here are some automated review suggestions for this pull request.

Reviewed commit: dcc6488fff

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

[cknitt]

@codex review

[github-actions]

Semantic diff: https://cdn.rescript-lang.org/semantic-diff/pr-8888/index.html?v=73d89ca3d

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 73d89ca3d5

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