From 2e9ca64ebfe8cef4ac44c5caec8070f55f58839e Mon Sep 17 00:00:00 2001 From: Anthony Ettinger Date: Sun, 6 Sep 2026 11:41:41 +0000 Subject: [PATCH] fix: sync STACK_VERSION with package.json for 0.2.0 The version lives in two places and #8 only bumped one, so main shipped package.json at 0.2.0 with STACK_VERSION still reading 0.1.3. The export contract test asserts the two match and fails on main. It passed in the PR because the suite was run before the version bump and not again after it. Adds a comment on the constant so the next release does not repeat the sequence. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01H5K2AxX2QZ98JW1Exe5wup --- src/index.ts | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/index.ts b/src/index.ts index 5178474..131c0d8 100644 --- a/src/index.ts +++ b/src/index.ts @@ -8,7 +8,10 @@ * The root entry intentionally exports almost nothing so importing it never * pulls framework code (next/react/supabase) into your bundle. */ -export const STACK_VERSION = "0.1.3"; +// Kept in step with package.json by hand; tests/contract asserts they match, +// so a release that bumps one and not the other fails there rather than +// shipping a package that misreports its own version. +export const STACK_VERSION = "0.2.0"; export const STACK_MODULES = [ "referrals", "email",