@clubedge/create-clubedge-app 0.41.0 → 0.41.1

package/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 All notable changes to `create-clubedge-app` are documented here.
 
+## 0.41.1
+
+- Default to Starter `v0.26.1` (#130): new projects' weekly upgrade workflow opens its pull request when the upgrade leaves conflict markers in a `package.json`, listing them, instead of stopping without one. It runs `upgrade --detailed-exit-code`, from 0.41.0. Existing projects get the workflow through their next upgrade pull request.
+
 ## 0.41.0
 
 - **A `package.json` with conflict markers no longer breaks the next commands** (#122, by @NishilRathod; issue #111):

package/README.md

@@ -141,7 +141,7 @@ They meet at one HTTP contract, `packages/contract/openapi.yaml`: the frontend c
 
 With `--auth supabase`, the Vite app owns the browser session and attaches its access token to contract requests. Hono or FastAPI verifies that token with Supabase Auth and returns the contract's shared user shape. Configure `VITE_SUPABASE_URL`, `VITE_SUPABASE_PUBLISHABLE_KEY`, `SUPABASE_URL`, and `SUPABASE_PUBLISHABLE_KEY` in the generated env examples; no Supabase service-role key goes to the browser.
 
-With the Hono API, the decoupled stacks support every module option the full-stack frameworks do (since Starter v0.26.0), each running in the API with the matching UI in the frontend; with FastAPI, they support Supabase Auth, Better Auth, Firebase, Appwrite, or `none`, plus memory cache. Both work with any local infrastructure (the API's `apps/api/.env.local` holds `DATABASE_URL`, since the API owns the database), and Docker or Railway deployment. With Docker, `pnpm clubedge deploy` writes a `compose.yaml` that builds the frontend and API as separate services; copy the variables of `.env.example` and `apps/api/.env.example` to `.env.production`, fill in their values, and run `docker compose --env-file .env.production up --build -d`. The frontend's `VITE_*` values are build arguments, compiled into its bundle; with Better Auth, its Node server also gets the auth variables (`DATABASE_URL`, `BETTER_AUTH_SECRET`, `BETTER_AUTH_URL`, and the email settings). With Railway, deploy provisions a public frontend and a private API, wires the frontend proxy to the API, and runs migrations before releasing the API. See [docs/stack-packs.md](docs/stack-packs.md) for how stacks and deployment facts are described.
+With the Hono API, the decoupled stacks support every module option the full-stack frameworks do (since Starter v0.26.1), each running in the API with the matching UI in the frontend; with FastAPI, they support Supabase Auth, Better Auth, Firebase, Appwrite, or `none`, plus memory cache. Both work with any local infrastructure (the API's `apps/api/.env.local` holds `DATABASE_URL`, since the API owns the database), and Docker or Railway deployment. With Docker, `pnpm clubedge deploy` writes a `compose.yaml` that builds the frontend and API as separate services; copy the variables of `.env.example` and `apps/api/.env.example` to `.env.production`, fill in their values, and run `docker compose --env-file .env.production up --build -d`. The frontend's `VITE_*` values are build arguments, compiled into its bundle; with Better Auth, its Node server also gets the auth variables (`DATABASE_URL`, `BETTER_AUTH_SECRET`, `BETTER_AUTH_URL`, and the email settings). With Railway, deploy provisions a public frontend and a private API, wires the frontend proxy to the API, and runs migrations before releasing the API. See [docs/stack-packs.md](docs/stack-packs.md) for how stacks and deployment facts are described.
 
 ## Choosing modules
 
@@ -207,7 +207,7 @@ pnpm dlx @clubedge/create-clubedge-app my-app --yes --no-git --framework tanstac
 pnpm dlx @clubedge/create-clubedge-app my-app --ref main
 
 # Reproduce a specific Starter release or commit
-pnpm dlx @clubedge/create-clubedge-app my-app --ref v0.26.0
+pnpm dlx @clubedge/create-clubedge-app my-app --ref v0.26.1
 pnpm dlx @clubedge/create-clubedge-app my-app --ref <commit-sha>
 
 # Test local Starter changes before releasing them
@@ -226,7 +226,7 @@ pnpm clubedge add email resend payments stripe              # several modules as
 pnpm clubedge remove storage payments
 pnpm dlx @clubedge/create-clubedge-app add infra local --dry-run
 pnpm dlx @clubedge/create-clubedge-app@latest upgrade        # to the newest CLI's Starter release
-pnpm dlx @clubedge/create-clubedge-app upgrade --ref v0.26.0 # or a specific tag, branch, or commit
+pnpm dlx @clubedge/create-clubedge-app upgrade --ref v0.26.1 # or a specific tag, branch, or commit
 ```
 
 The CLI renders the project twice, from the Starter commit and modules recorded in your `package.json` and from the new state, and merges the difference into your project. The new state has other modules for `add` and `remove`, and the newer Starter with the same modules for `upgrade`. Modules a newer Starter introduces start as `none` where possible, so an upgrade never adds a service on its own.
@@ -341,27 +341,27 @@ Projects created with `--infra neon` also have `.github/workflows/preview.yml`,
 Each CLI release is tested against one specific Starter release:
 
 ```text
-create-clubedge-app v0.41.0
+create-clubedge-app v0.41.1
         |
         v
-Clubedge Starter v0.26.0
-commit 7c01a0295bea53adc72bda5b843a478ddd04f892
+Clubedge Starter v0.26.1
+commit 93429784e265c9dc8eb8f8c87169e7b42732719f
 ```
 
 The current relationship is:
 
 | CLI release | Default Starter release | Meaning |
 | --- | --- | --- |
-| `create-clubedge-app@0.41.0` | `clubedge-starter@v0.26.0` | The CLI's required, tested default |
+| `create-clubedge-app@0.41.1` | `clubedge-starter@v0.26.1` | The CLI's required, tested default |
 
 This means the same CLI version always scaffolds the same Starter revision by default. The CLI does not silently follow Starter `main`.
 
-The `v0.26.0` tag is expected to resolve to commit
-`7c01a0295bea53adc72bda5b843a478ddd04f892`. The CLI verifies this before
+The `v0.26.1` tag is expected to resolve to commit
+`93429784e265c9dc8eb8f8c87169e7b42732719f`. The CLI verifies this before
 scaffolding with the default reference and fails rather than silently using a
 moved tag.
 
-When the Starter changes, its maintainers first publish a new versioned release, such as `v0.26.0`. The CLI is then updated to use that release, all generated-project checks must pass, and a new CLI version is published. This keeps Starter and CLI releases independently versioned while preserving a tested compatibility relationship.
+When the Starter changes, its maintainers first publish a new versioned release, such as `v0.26.1`. The CLI is then updated to use that release, all generated-project checks must pass, and a new CLI version is published. This keeps Starter and CLI releases independently versioned while preserving a tested compatibility relationship.
 
 Every generated project records its CLI version, Starter repository, Starter ref, Starter commit, framework, and modules in `package.json` and `README.md`.
 
@@ -416,7 +416,7 @@ CI packs the CLI with `npm pack`, scaffolds clean projects from the packed tarba
 1. Make and validate changes in `clubedge-starter`.
 2. Run lint, typecheck, unit tests, browser tests, and production build.
 3. Update the Starter package versions.
-4. Commit `main`, create a release tag such as `v0.26.0`, and publish the Starter release.
+4. Commit `main`, create a release tag such as `v0.26.1`, and publish the Starter release.
 
 ### CLI maintainers
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/create-clubedge-app",
-  "version": "0.41.0",
+  "version": "0.41.1",
   "description": "Create React apps from Clubedge Starter with a CLI or local MCP server.",
   "type": "module",
   "packageManager": "pnpm@10.9.0",
@@ -24,8 +24,8 @@
   },
   "clubedge": {
     "starterRepository": "Clubedge/clubedge-starter",
-    "starterRef": "v0.26.0",
-    "starterCommit": "7c01a0295bea53adc72bda5b843a478ddd04f892"
+    "starterRef": "v0.26.1",
+    "starterCommit": "93429784e265c9dc8eb8f8c87169e7b42732719f"
   },
   "license": "Apache-2.0",
   "repository": {

package/template/.github/workflows/clubedge-upgrade.yml

@@ -37,14 +37,50 @@ jobs:
         id: upgrade
         shell: bash
         run: |
-          before=$(node -p "require('./package.json').clubedge?.starterRef ?? ''")
+          # A field of `clubedge` in package.json, read with fs: while a package.json has conflict
+          # markers, require() fails for every file in the project, and pnpm cannot read it. After
+          # an upgrade that left them, the Starter's version saved in .clubedge/incoming has the
+          # new values; pass it as the fallback.
+          starter_field() {
+            node -e '
+              const fs = require("node:fs");
+              const [field, fallback] = process.argv.slice(1);
+              const read = (file) => JSON.parse(fs.readFileSync(file, "utf8"));
+              let manifest;
+              try {
+                manifest = read("package.json");
+              } catch (error) {
+                if (!fallback) {
+                  console.error(`package.json could not be read (${error.message}). Fix it on the default branch, then run this workflow again.`);
+                  process.exit(1);
+                }
+                try {
+                  manifest = read(fallback);
+                } catch {
+                  console.error(`Neither package.json nor ${fallback} could be read after the upgrade.`);
+                  process.exit(1);
+                }
+              }
+              console.log(manifest.clubedge?.[field] ?? "");
+            ' "$@"
+          }
+
+          before=$(starter_field starterRef)
           if [ -z "$before" ]; then
             echo "package.json records no Starter release: this project was not created by create-clubedge-app."
             exit 1
           fi
-          # The newest CLI upgrades to the Starter release it is pinned to.
-          pnpm dlx @clubedge/create-clubedge-app@latest upgrade --no-install 2>&1 | tee "$RUNNER_TEMP/upgrade.log"
-          after=$(node -p "require('./package.json').clubedge.starterRef")
+          # The newest CLI upgrades to the Starter release it is pinned to. With
+          # --detailed-exit-code it exits with 2 when the upgrade left conflicts to resolve, which
+          # the pull request lists; any other failure stops here.
+          status=0
+          pnpm dlx @clubedge/create-clubedge-app@latest upgrade --no-install --detailed-exit-code 2>&1 | tee "$RUNNER_TEMP/upgrade.log" || status=$?
+          if [ "$status" -ne 0 ] && [ "$status" -ne 2 ]; then
+            echo "The upgrade failed (exit code $status); nothing was pushed."
+            exit "$status"
+          fi
+          after=$(starter_field starterRef .clubedge/incoming/package.json)
+          repository=$(starter_field starterRepository .clubedge/incoming/package.json)
           if [ "$after" = "$before" ] && [ -z "$(git status --porcelain)" ]; then
             echo "Already on the newest Starter release, $before."
             exit 0
@@ -54,12 +90,21 @@ jobs:
             echo "$branch already exists: its pull request is open, or was closed on purpose."
             exit 0
           fi
-          # The lockfile follows the upgraded package.json files; a conflict there can stop it.
-          install="updated"
-          pnpm install --no-frozen-lockfile >"$RUNNER_TEMP/install.log" 2>&1 || install="failed"
+          conflicts=""
+          if [ "$status" -eq 2 ]; then conflicts=$(git grep -l --untracked '^<<<<<<< yours' -- . || true); fi
+          # The lockfile follows the upgraded package.json files. pnpm cannot read one with
+          # conflict markers, so the install waits until they are resolved.
+          if printf '%s\n' "$conflicts" | grep -qE '(^|/)package\.json$'; then
+            install="skipped"
+          else
+            install="updated"
+            pnpm install --no-frozen-lockfile >"$RUNNER_TEMP/install.log" 2>&1 || install="failed"
+          fi
+          printf '%s\n' "$conflicts" | sed '/^$/d' >"$RUNNER_TEMP/conflicts.txt"
           {
             echo "before=$before"
             echo "after=$after"
+            echo "repository=${repository:-Clubedge/clubedge-starter}"
             echo "branch=$branch"
             echo "install=$install"
             if [ -d .clubedge/incoming ]; then echo "incoming=true"; fi
@@ -79,21 +124,17 @@ jobs:
           OWN_TOKEN: ${{ secrets.CLUBEDGE_UPGRADE_TOKEN != '' }}
           BEFORE: ${{ steps.upgrade.outputs.before }}
           AFTER: ${{ steps.upgrade.outputs.after }}
+          REPOSITORY: ${{ steps.upgrade.outputs.repository }}
           BRANCH: ${{ steps.upgrade.outputs.branch }}
           INSTALL: ${{ steps.upgrade.outputs.install }}
+          DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
           RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
         run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
-          git switch --create "$BRANCH"
-          git add --all
-          git commit --quiet --message "chore: upgrade to Clubedge Starter $AFTER"
-          git push --quiet --set-upstream origin "$BRANCH"
-
-          repository=$(node -p "require('./package.json').clubedge.starterRepository ?? 'Clubedge/clubedge-starter'")
-          conflicts=$(git grep -l '^<<<<<<< yours' -- . || true)
+          # The pull request's text is written before anything is pushed: it reads nothing from
+          # the upgraded files, whose package.json may have conflict markers.
+          conflicts=$(cat "$RUNNER_TEMP/conflicts.txt")
           {
-            echo "Upgrades this project from Clubedge Starter \`$BEFORE\` to [\`$AFTER\`](https://github.com/$repository/releases/tag/$AFTER), with \`pnpm clubedge upgrade\`. Your own edits are merged in; files you never changed take the new version."
+            echo "Upgrades this project from Clubedge Starter \`$BEFORE\` to [\`$AFTER\`](https://github.com/$REPOSITORY/releases/tag/$AFTER), with \`pnpm clubedge upgrade\`. Your own edits are merged in; files you never changed take the new version."
             echo
             if [ -n "$conflicts" ]; then
               echo "### Conflicts to resolve"
@@ -105,15 +146,20 @@ jobs:
               echo "The Starter's whole new version of each is in the **starter-versions** artifact of [the run]($RUN_URL), to compare with yours."
               echo
             fi
-            if [ "$INSTALL" = "failed" ]; then
+            if [ "$INSTALL" = "skipped" ]; then
+              echo "### pnpm install"
+              echo
+              echo "\`pnpm install\` did not run: pnpm cannot read a \`package.json\` with conflict markers, so \`pnpm-lock.yaml\` and \`pnpm clubedge\` wait for them. Resolve the conflicts in the \`package.json\` files above, then run \`pnpm install\` and commit \`pnpm-lock.yaml\`."
+              echo
+            elif [ "$INSTALL" = "failed" ]; then
               echo "### pnpm install"
               echo
-              echo "\`pnpm install\` did not complete on the upgraded project, usually because of a conflict in a \`package.json\`. Resolve it, then run \`pnpm install\` and commit \`pnpm-lock.yaml\`."
+              echo "\`pnpm install\` did not complete on the upgraded project, so \`pnpm-lock.yaml\` is not updated. Run \`pnpm install\` to see why, then commit \`pnpm-lock.yaml\`."
               echo
             fi
             echo "### Before merging"
             echo
-            echo "- Read the [release notes](https://github.com/$repository/releases/tag/$AFTER) for anything to do by hand."
+            echo "- Read the [release notes](https://github.com/$REPOSITORY/releases/tag/$AFTER) for anything to do by hand."
             echo "- Run \`pnpm db:migrate\` for new migrations, and your tests."
             echo
             echo "<details><summary>Upgrade output</summary>"
@@ -126,8 +172,21 @@ jobs:
             echo
             echo "Opened by the Starter upgrade workflow (\`.github/workflows/clubedge-upgrade.yml\`)."
           } >"$RUNNER_TEMP/body.md"
-          gh pr create --base "${{ github.event.repository.default_branch }}" --head "$BRANCH" \
-            --title "chore: upgrade to Clubedge Starter $AFTER" --body-file "$RUNNER_TEMP/body.md"
+
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git switch --create "$BRANCH"
+          git add --all
+          git commit --quiet --message "chore: upgrade to Clubedge Starter $AFTER"
+          git push --quiet --set-upstream origin "$BRANCH"
+          # A pushed branch without its pull request would make every later run skip this release,
+          # so it is deleted for the next run to try again.
+          if ! gh pr create --base "$DEFAULT_BRANCH" --head "$BRANCH" \
+            --title "chore: upgrade to Clubedge Starter $AFTER" --body-file "$RUNNER_TEMP/body.md"; then
+            echo "::error::The pull request could not be opened, so $BRANCH is deleted and the next run tries again."
+            git push --quiet origin --delete "$BRANCH" || echo "::warning::Delete $BRANCH by hand, or later runs skip $AFTER."
+            exit 1
+          fi
           # Pull requests opened with the default token start no workflows: start CI on the branch.
           if [ "$OWN_TOKEN" != "true" ] && [ -f .github/workflows/ci.yml ]; then
             gh workflow run ci.yml --ref "$BRANCH" || echo "Start CI on $BRANCH by hand."

package/template/apps/api/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/api",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/apps/api-fastapi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/api-fastapi",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/apps/api-fastapi/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "clubedge-api"
-version = "0.26.0"
+version = "0.26.1"
 description = "The project's API, implementing packages/contract/openapi.yaml."
 requires-python = ">=3.12"
 dependencies = [

package/template/apps/api-fastapi/uv.lock

@@ -304,7 +304,7 @@ wheels = [
 
 [[package]]
 name = "clubedge-api"
-version = "0.26.0"
+version = "0.26.1"
 source = { editable = "." }
 default-groups = "all"
 dependencies = [

package/template/apps/start/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/start",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/apps/vite/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/vite",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/apps/web/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/web",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "scripts": {

package/template/clubedge.template.json

@@ -74,6 +74,7 @@
     "scripts/stack-preview-render.mjs",
     "scripts/stack-preview-generate.mjs",
     "scripts/stack-preview-supabase.mjs",
+    "scripts/clubedge-upgrade-workflow.test.ts",
     "scripts/template-manifest.test.ts",
     "scripts/vite-api-routes.test.ts"
   ]

package/template/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clubedge-starter-v1",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "packageManager": "pnpm@10.9.0",

package/template/packages/auth/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/auth",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/packages/auth-appwrite/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/auth-appwrite",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Appwrite provider for @clubedge/auth, run from the server with an API key and session cookies.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/auth-better-auth/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/auth-better-auth",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Better Auth adapter for @clubedge/auth, storing users and sessions in your own PostgreSQL.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/auth-firebase/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/auth-firebase",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Firebase Authentication provider for @clubedge/auth, run from the server with session cookies.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/auth-supabase/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/auth-supabase",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Supabase Auth adapter for @clubedge/auth.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/cache/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/cache",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/packages/cache-redis/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/cache-redis",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Redis rate limiter and cache for @clubedge/cache.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/contract/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/contract",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/packages/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/core",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/packages/db/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/db",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/packages/email/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/email",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Email interface, console and in-memory providers, and message templates.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/email-resend/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/email-resend",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Resend provider for @clubedge/email, through Resend's HTTP API.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/email-smtp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/email-smtp",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "SMTP provider for @clubedge/email, for any SMTP server.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/jobs/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/jobs",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Background jobs interface: job definitions, a queue contract, and an in-memory queue.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/jobs-bullmq/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/jobs-bullmq",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "BullMQ provider for @clubedge/jobs: a job queue stored in Redis.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/jobs-inngest/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/jobs-inngest",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Inngest provider for @clubedge/jobs: jobs run by Inngest, which calls the app for each one.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/jobs-pg-boss/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/jobs-pg-boss",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "pg-boss provider for @clubedge/jobs: a job queue stored in the project's PostgreSQL.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/local-db/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/local-db",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "PostgreSQL for development without Docker: PGlite served over the PostgreSQL protocol.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/observability/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/observability",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Observability interface: error reports and spans for @clubedge/core's telemetry hooks, and an in-memory provider for tests.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/observability-otel/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/observability-otel",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "OpenTelemetry provider for @clubedge/observability: traces and error logs exported over OTLP to any collector.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/observability-sentry/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/observability-sentry",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Sentry provider for @clubedge/observability: server and browser errors, traces, and source map uploads.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/payments/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/payments",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Provider-neutral payments: the PaymentProvider interface, billing logic, and subscription tables.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/payments-stripe/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/payments-stripe",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Stripe provider for @clubedge/payments: Checkout, the customer portal, and verified webhooks.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/storage/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/storage",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template/packages/storage-s3/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/storage-s3",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "S3-compatible adapter for @clubedge/storage.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/storage-supabase/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/storage-supabase",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Supabase Storage adapter for @clubedge/storage.",
   "private": true,
   "license": "Apache-2.0",

package/template/packages/ui/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clubedge/ui",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "private": true,
   "license": "Apache-2.0",
   "type": "module",

package/template.lock.json

@@ -1,7 +1,7 @@
 {
   "repository": "Clubedge/clubedge-starter",
-  "ref": "v0.26.0",
-  "commit": "7c01a0295bea53adc72bda5b843a478ddd04f892",
+  "ref": "v0.26.1",
+  "commit": "93429784e265c9dc8eb8f8c87169e7b42732719f",
   "files": [
     ".dockerignore",
     ".env.example",