@bevel-software/platform-core-backend 0.9.1 → 0.10.0

package/src/version.ts

@@ -1,3 +1,5 @@
+import { readFileSync } from 'node:fs';
+
 /**
  * The git commit the running build was produced from, surfaced by
  * `GET /api/health` so the deploy pipeline can confirm a staging/production
@@ -17,3 +19,29 @@ export function resolveGitSha(env: NodeJS.ProcessEnv = process.env): string {
 }
 
 export const GIT_SHA = resolveGitSha();
+
+/**
+ * The RELEASE version of the running build — this package's own `version`
+ * field, which the fixed-group release process keeps equal to the deployment's
+ * release tag (`v<version>`). This is what the update check compares against
+ * the newest published release; the git sha above identifies a build, but two
+ * shas can't tell "behind" from "ahead".
+ *
+ * Read from the packaged `package.json`, one hop up from this module in both
+ * layouts (`src/` in-repo and tsx, `dist/` compiled — same trick as
+ * `assets.ts`). Lazily and defensively: a build that somehow ships without a
+ * readable manifest answers `'unknown'`, which the update check treats as
+ * "never announce an update" rather than an error.
+ */
+export function resolveAppVersion(): string {
+  try {
+    const manifest = JSON.parse(
+      readFileSync(new URL('../package.json', import.meta.url), 'utf8'),
+    ) as { version?: unknown };
+    return typeof manifest.version === 'string' && manifest.version
+      ? manifest.version
+      : 'unknown';
+  } catch {
+    return 'unknown';
+  }
+}