CrabStack 1.0.0
Released 2026-11-11. This is the first tagged release of the template.
Until now, buyers took changes by merging main. From here on, each release gets a tag, a dated section in CHANGELOG.md, and a page in this section. If you already merged main, you have most of 1.0.0.
To take it, merge the tag upstream/v1.0.0, not upstream/main, because main already carries the next release's migration (see Next). Updating from upstream has the steps. Its step 1 now fetches the template's tags as upstream/v*, so they cannot clash with tags of your own: if you added the remote before, run its two config lines once.
Security fixes
The last round before the tag fixed these:
- When the database URL asks for certificate checks, the backend now does them.
sslmode=verify-fullchecks the certificate chain and the hostname, andverify-cachecks the chain against the newDATABASE_CA_CERT. Before, the backend droppedsslmodeand connected without checking the certificate.requirestill encrypts without verifying, anddisablenow turns TLS off. See Database TLS. - The sessions table stores a SHA-256 hash of each session token, so a leaked dump, backup or replica no longer hands out working sign-ins. Migration 023 converts existing sessions in place, so nobody is signed out.
- SMTP requires TLS, both for the backend's own email and for magic-link sign-in. Before, a network attacker who stripped STARTTLS from the server's greeting got the SMTP login and every message in cleartext, including live magic-link URLs that sign in whoever opens them. A loopback host is exempt, and
SMTP_REQUIRE_TLS=falseandEMAIL_SERVER_REQUIRE_TLS=falseturn it off for an internal relay. - A request that one IP address sends past its own magic-link limit no longer counts against the email address it names.
- The admin MCP server's sign-in flow caps the authorization codes each user can hold open, so one user can no longer fill the pool that every user's codes share.
Before you deploy
The "Breaking / action required" list in the 1.0.0 section of CHANGELOG.md is the work to do by hand. The newest items:
- If your
DATABASE_URLsaysverify-ca, or saysverify-fullagainst a CA that Node does not trust, setDATABASE_CA_CERTto that CA's PEM. On DigitalOcean App Platform that is${db.CA_CERT}. Ansslmodethe backend does not recognise now stops it at boot. - Code of yours that reads
sessions.session_tokenmust usesession_token_hashandhashSessionToken(). Rolling migration 023 back signs everyone out, because a hash cannot be turned back into the token. - An SMTP server that offers no TLS gets no mail unless you set both opt-outs above. Port 465 needs implicit TLS: set
SMTP_SECURE=truefor the backend andEMAIL_SERVER_SECURE=truefor the frontend. - Migration 022 makes six columns that always had defaults
NOT NULL, and rewrites any null already stored in them to the column's default. types.integration.spec.tschecks every table against its row interface and fails on a table it does not list, so add your own tables to itsROW_TYPES. CI now also rolls every migration back and forward again, so a migration of yours whosedown()throws or is missing fails the build.
Migration 023 renames a column that the running backend reads. During a deploy that runs migrations before replacing the old backend, sign-in and every signed-in request fail from the moment migrations run until the new backend serves traffic.
Next
The next release drops the unused blog_posts.views column. A backend older than 1.0.0 may still write to it, so deploy 1.0.0 before you take the next one.