Skip to content

fix: use canonical Forge version across system surfaces - #89

Merged
Codename-11 merged 1 commit into
mainfrom
codex/axi-154-canonical-build-version
Jul 25, 2026
Merged

Codename-11 merged 1 commit into
mainfrom
codex/axi-154-canonical-build-version

Conversation

@Codename-11

Copy link
Copy Markdown
Owner

Summary

  • make Admin System use Forge's shared build identity instead of the production 1.0.0 fallback
  • make the sign-in footer read the packaged application version
  • document the canonical version source and add unit plus Postgres-backed router regression coverage

Root cause

instanceAdmin.system read npm_package_version directly. That lifecycle variable is absent in the standalone production runtime, so the router returned its hardcoded 1.0.0 fallback even though package.json and system.buildInfo correctly reported 0.29.7.

Validation

  • pnpm vitest run tests/unit/build-info.test.ts
  • DATABASE_URL=postgresql://forge:forge@localhost:55432/forge?schema=public REDIS_URL=redis://localhost:56379 pnpm vitest run src/server/routers/__tests__/instance-admin-system.test.ts
  • pnpm lint (passes with pre-existing warnings)
  • pnpm typecheck
  • pnpm docs:build
  • git diff --check

Delivery

Implements AXI-154. This PR intentionally contains no version bump, release tag, or deployment change.

@Codename-11
Codename-11 merged commit 7289380 into main Jul 25, 2026
5 of 6 checks passed
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.

1 participant