OpenClaw moved closer to its next stable build Monday night with the merge of PR #160775, titled chore(release): prepare 2026.9.7.
This is not a public release tag yet. The latest GitHub release remains v2026.9.6 as of the 23:00 UTC nightly sweep. But the merged release-prep PR is a strong signal that 2026.9.7 has entered the validation lane with aligned versions, generated notes, and a trusted same-repository merge.
What Changed
The PR aligns OpenClaw's root, plugin, and macOS versions to 2026.9.7. It also adds the release-note material for the candidate build.
According to the PR body, the prepared notes include:
- 8 highlights.
- 70 changes.
- 207 fixes.
- A complete contribution record.
- 2,770 verified PRs since the
2026.9.6cut, excluding work already shipped inv2026.9.6.
The release branch was re-cut at main commit fb503c9e1f25. The merged PR becomes the release SHA, with the code SHA and release SHA intentionally matching for Full Release Validation.
Why It Matters
Release-prep PRs are easy to dismiss as paperwork, but in OpenClaw's current release process they are a real checkpoint. They bind the candidate version, changelog, release notes, and contributor ledger before validation starts treating the candidate as a publishable artifact.
That matters because OpenClaw releases touch many surfaces: the CLI, Gateway, plugins, native apps, channels, model extensions, and docs. A clean release ledger makes it easier for operators to answer the basic question after upgrade day: what exactly changed?
It is also notable that this prep follows the 2026.9.6 release warning for macOS app updates. A 2026.9.7 candidate may be important for users waiting on the next stable fix path, but the PR itself does not claim the public release is available yet.
Verification
The PR reports three release-preparation checks:
pnpm release:prepare -- --version 2026.9.7 --write, followed by--check, passed.verify-release-notes.mjsverified 2,770 PRs against the shippedv2026.9.6reference.pnpm changelog:checkandgit diff --checkpassed.
One contextual reference, #155121, is noted as a GitHub-deleted reference. The PR records that exception rather than silently dropping it.
What To Watch Next
The next important signal is the actual v2026.9.7 release tag and its publication evidence. Until that appears, this should be treated as release-candidate preparation rather than an install recommendation.
For OpenClaw watchers, though, the direction is clear: the 2026.9.7 train has a prepared release branch, a candidate ledger, and validation inputs ready to run.