Skip to content

Release Better Stack v3.0.0 - #256

Merged
olliethedev merged 435 commits into
mainfrom
v3
Sep 1, 2026
Merged

Release Better Stack v3.0.0#256
olliethedev merged 435 commits into
mainfrom
v3

Conversation

@olliethedev

@olliethedev olliethedev commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

Promotes the complete reviewed v3 line to main for the stable 3.0.0 release.

  • removes the legacy dual paths tracked by Phase 3: remove legacy dual paths and release v3.0.0 #137
  • includes the final runtime, authorization, provider, lifecycle, and codegen contracts
  • aligns the stable Better Auth 1.6.16 cohort and optional Better Auth UI 2.0.0 scaffold
  • sets @btst/stack@3.0.0 and @btst/codegen@0.2.0
  • includes the stable migration and production verification playbook

Release evidence

  • stable prep: chore: prepare v3.0.0 stable release #255
  • full CI, lint, typecheck, build, knip, and tests: green
  • packed consumers: npm/pnpm × core/auth all green
  • init and Better Auth UI fixtures: Next.js, React Router, and TanStack green
  • registry clean-room validation: green
  • browser codegen E2E: all three frameworks green
  • Standards review: no violations
  • Spec review: no findings

Release procedure

Merge with a merge commit so the exact main integration SHA can be tagged v3.0.0. After main CI is green, publish through the trusted release workflow, verify provenance and public clean installs, deploy the stable cohort in Better Stack Web, and only then close #153 and #137.

…ation

feat(kanban): unify authorization operations
olliethedev and others added 25 commits August 29, 2026 11:18
docs(v3): publish canonical DX migration guide
…seams

Remove legacy seams and verify all plugins
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
* test: add packed consumer compatibility smoke

* test: complete packed auth consumer coverage

* refactor: share packed consumer dependencies

* test: reject split auth type universes

* ci: isolate Better Auth UI fixture install
@vercel

vercel Bot commented Sep 1, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
Project Deployment Actions Updated
better-stack-docs Ignored Ignored Sep 1, 2026 1:02am UTC
better-stack-playground Ignored Ignored Sep 1, 2026 1:02am UTC

Request Review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-01T01:18:09.761996Z f967b03 PR opened
ℹ️ 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.

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Shadcn registry validated — no registry changes detected.

@olliethedev
olliethedev merged commit 32e9f36 into main Sep 1, 2026
14 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f967b0374a

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

{ field: "updatedAt", value: claimedAt, operator: "eq" as const },
],
});
if (deleted !== 1) throw staleFormError();

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Normalize deleteMany results before declaring stale state

When a supported adapter returns a driver-style success value such as { count: 1 } or { affectedRows: 1 }, this strict comparison treats the successful deletion as stale, throws, and rolls back the transaction, so deleting forms fails on those adapters. Use the existing didAffectRow normalization here and for the equivalent submission deletion check.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[v3] Resolve RC3 findings and publish stable v3

1 participant