[objectstack-fleet]

Requested by 田騏 · project thread

Summary

18.1.0 is published. This PR does the follow-up work the 18.1 page was waiting on. It is docs-only.

Release facts, as measured. This is a new section, measured with npm view / npm pack on 2026-10-24:

• npm tags: latest is 18.1.0 on every package read. next still points at the older 18.0.0-next.5, and rc at 17.0.0-rc.6.
• Publish: npm at 09:06 UTC, followed by 73 per-package GitHub Releases.
• Version commit: e649c2d91e (chore: version packages #25606), after the reverted first cut (fix(release): revert the red 18.1.0 version commit and fix the dogfood proof that reddened it #25605).

The section also carries two cautions:

• 260 of the 265 CHANGELOG entries cite 3937697. That is the commit that reverted the first cut, not each entry's own commit. The published tarballs carry the same attribution: every entry in @objectstack/cli@18.1.0's 18.1.0 section reads 3937697.
• An exact pin still floats. @objectstack/cli declares eight @objectstack/* dependencies as workspace:^, which publishes as a caret range. An app pinned to exactly 18.0.0 therefore installed 17 packages at 18.1.0 today. The checklist gives the pnpm override that holds them, and that override was measured.

Counts. These are read off the published sections: 265 distinct entries, split 82 / 9 / 50 / 2 / 122 across the five sections. 91 changesets are declared breaking, 48 minor and 43 patch. The pre-cut count of 258 was low because entries whose first line is identical were merged; once every first line began with the same revert commit, the eight "Shipped in 18.0.0" entries collapsed into one.

Upgrade checklist, walked. I walked one create-objectstack@18.0.0 blank app on SQLite under single. It had an administrator and three notes, and was moved to 18.1.0. Each line the walk measured is marked:

• the pins and the override
• the os serve refusal without a secret, and os start minting .objectstack/auth-secret instead
• the 18.0.0 session still being valid when the same secret is used
• validate and build passing
• migrate meta --from 17, which lists 417 manual changes; --from 18 replays nothing
• migrate meta --stored
• migrate plan: 33 nullable tenant columns, schema in sync
• probes of the confirmText refusal (422) and the rollback toVersion refusal (400)

The callout lists what was not walked.

Folded in. #25591, #25592 (breaking) and #25596, the last changesets before the cut.

Checks

These pass locally:

• check:role-word
• check:release-notes
• check:release-page-status
• check:release-index-currency-sync
• check:doc-anchors
• check:docs-audit-scope
• check:docs-single-h1
• check:docs-redirects
• check:doc-authoring
• check:error-code-casing
• check:cli-examples-parity
• an MDX compile of both changed v18 pages

Clause-②: no
Metadata-protocol: none

🤖 Generated with Claude Code

https://claude.ai/code/session_01At7xrR4rgknXtej5ZkMJHd