Enter changesets pre-release mode (rc) → cut Stack family 1.0.0-rc.0

[coderdan]

Summary

Enter changesets pre-release mode (rc tag) and add a major changeset for the Stack 1.0 family so the next release cuts 1.0.0-rc.0.

Scope

• .changeset/pre.json — enter pre mode with tag rc.
• .changeset/stack-1-0-0-rc.md — a major changeset for @cipherstash/stack, @cipherstash/stack-drizzle, @cipherstash/stack-supabase, and stash.

Verified: those four resolve to 1.0.0-rc.0; other packages with pending changesets take their own bump with an -rc.0 suffix (e.g. @cipherstash/schema → 3.0.2-rc.0).

Release flow after merge

1. changesets/action opens/updates a "Version Packages" PR showing 1.0.0-rc.0 for the four — that PR is the review gate; nothing publishes until it's merged.
2. Merging it runs pnpm run release → publishes under the rc npm dist-tag (pre mode does this automatically; latest stays on current stable).

Publishing prerequisites

• New-package bootstrap: @cipherstash/stack-drizzle and @cipherstash/stack-supabase had never been published, so npm OIDC trusted publishing couldn't authenticate them. Both are now bootstrapped with trusted publishing configured. No release.yml change; deliberately no NPM_TOKEN (it would shadow OIDC and fail the run — OIDC trusted publishing E404 when publishing scoped packages from changesets/action npm/cli#8976).

⚠️ Caveat

Pre mode is repo-wide and sticky to main: while pre.json is on main, every package with pending changesets publishes as -rc.N under the rc tag, and successive merges yield rc.1, rc.2, … For GA: pnpm changeset pre exit, PR to main, merge.

Resolution

Done in #647.

[coderdan]

Resolved by #647 (merged).