@exadev/build-identity 2.1.0 → 2.2.0

package/README.md

@@ -118,6 +118,23 @@ const predictedVersion = await predictNextVersion(process.cwd(), releaseRules, a
 const identity = resolvePredictedIdentity(build, predictedVersion);
 ```
 
+## `readPackageVersion(repoRoot)`
+
+```ts
+function readPackageVersion(repoRoot: string): string;
+```
+
+The plain `"version"` field from `package.json` at `repoRoot`, read unconditionally and with no git access at all. This is deliberately not the same thing as `resolveBuildIdentity(...).version`, which is a build *identity* -- the released version only when a tag genuinely points at HEAD, and a short commit hash otherwise. Reach for this one when you want the last released semantic version regardless of whether this checkout happens to be sitting on its tag: an OpenAPI document's `info.version`, a user agent string, anything wanting a stable semver rather than an honest answer about what is deployed.
+
+Throws rather than defaulting when `package.json` is missing or its `"version"` is absent, non-string, or empty -- the same stance every other export in this package takes. `defaultTagName` (`v${version}`) is the shared convention `resolveBuildIdentity` and `predictNextVersion` both apply to this value.
+
+```ts
+import { readPackageVersion, resolveBuildIdentity } from '@exadev/build-identity';
+
+const appVersion = readPackageVersion(process.cwd()); // "1.4.0", tagged or not
+const build = resolveBuildIdentity(process.cwd(), 'exadev/example'); // "1.4.0" or "a1b2c3d"
+```
+
 ## `build-identity` (CLI)
 
 The same three functions, wired together, as a command. It exists for build and deploy steps that are a shell invocation rather than a JavaScript config file, so nothing in them can `import` this package at all -- `wrangler deploy --var RELEASE_VERSION:...` being the case it was built for. A step that *is* a JavaScript config file (`next.config.ts`, `vite.config.ts`) should import the functions directly instead; see [Framework-agnosticism](#framework-agnosticism) below.

package/dist/cli.js

@@ -5,7 +5,7 @@ import { Command, InvalidArgumentError, Option } from "commander";
 import { join } from "node:path";
 import { execFileSync } from "node:child_process";
 //#region package.json
-var version = "2.1.0";
+var version = "2.2.0";
 //#endregion
 //#region src/format-identity.ts
 const OUTPUT_FORMATS = ["json", "env"];

package/dist/index.cjs

@@ -204,5 +204,6 @@ async function loadCommitAnalyzer() {
 //#endregion
 exports.loadCommitAnalyzer = loadCommitAnalyzer;
 exports.predictNextVersion = predictNextVersion;
+exports.readPackageVersion = readPackageVersion;
 exports.resolveBuildIdentity = resolveBuildIdentity;
 exports.resolvePredictedIdentity = resolvePredictedIdentity;

package/dist/index.d.cts

@@ -105,4 +105,8 @@ declare function predictNextVersion(repoRoot: string, releaseRules: readonly Rel
  */
 declare function loadCommitAnalyzer(): Promise<AnalyzeCommits>;
 //#endregion
-export { type AnalyzeCommits, type BuildIdentity, type DisplayIdentity, type PredictNextVersionOptions, type ReleaseLevel, type ReleaseRule, type ResolveBuildIdentityOptions, loadCommitAnalyzer, predictNextVersion, resolveBuildIdentity, resolvePredictedIdentity };
+//#region src/package-version.d.ts
+/** The single semantic-release-managed version, read from `package.json` at `repoRoot`'s root -- shared by `resolveBuildIdentity` (what this build's version is, if released) and `predictNextVersion` (the version to diff commits since). Throws rather than defaulting, matching this package's own "no sensible placeholder identity" stance. */
+declare function readPackageVersion(repoRoot: string): string;
+//#endregion
+export { type AnalyzeCommits, type BuildIdentity, type DisplayIdentity, type PredictNextVersionOptions, type ReleaseLevel, type ReleaseRule, type ResolveBuildIdentityOptions, loadCommitAnalyzer, predictNextVersion, readPackageVersion, resolveBuildIdentity, resolvePredictedIdentity };

package/dist/index.d.ts

@@ -105,4 +105,8 @@ declare function predictNextVersion(repoRoot: string, releaseRules: readonly Rel
  */
 declare function loadCommitAnalyzer(): Promise<AnalyzeCommits>;
 //#endregion
-export { type AnalyzeCommits, type BuildIdentity, type DisplayIdentity, type PredictNextVersionOptions, type ReleaseLevel, type ReleaseRule, type ResolveBuildIdentityOptions, loadCommitAnalyzer, predictNextVersion, resolveBuildIdentity, resolvePredictedIdentity };
+//#region src/package-version.d.ts
+/** The single semantic-release-managed version, read from `package.json` at `repoRoot`'s root -- shared by `resolveBuildIdentity` (what this build's version is, if released) and `predictNextVersion` (the version to diff commits since). Throws rather than defaulting, matching this package's own "no sensible placeholder identity" stance. */
+declare function readPackageVersion(repoRoot: string): string;
+//#endregion
+export { type AnalyzeCommits, type BuildIdentity, type DisplayIdentity, type PredictNextVersionOptions, type ReleaseLevel, type ReleaseRule, type ResolveBuildIdentityOptions, loadCommitAnalyzer, predictNextVersion, readPackageVersion, resolveBuildIdentity, resolvePredictedIdentity };

package/dist/index.js

@@ -201,4 +201,4 @@ async function loadCommitAnalyzer() {
 	return commitAnalyzerModule.analyzeCommits;
 }
 //#endregion
-export { loadCommitAnalyzer, predictNextVersion, resolveBuildIdentity, resolvePredictedIdentity };
+export { loadCommitAnalyzer, predictNextVersion, readPackageVersion, resolveBuildIdentity, resolvePredictedIdentity };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exadev/build-identity",
-  "version": "2.1.0",
+  "version": "2.2.0",
   "description": "Resolve a build's true identity (a real release tag, or the commit it was built from) from git state, with an optional predicted-version display layer",
   "type": "module",
   "sideEffects": false,