Files
inbuxa-webmail/scripts/version.d.mts
T
jcoffey-dev 76ee66f106
ci / node (pull_request) Skipped
ci / version (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 2m42s
ci / docker-build (pull_request) Skipped
ci / publish (pull_request) Skipped
ci / announce (pull_request) Skipped
Number the webmail with the suite: 27.1-rc.1
The webmail moves from dated versions (2026.10.26+gcff6f1f) to the INBUXA
suite's release numbers: 27.1 for a series, 27.1.3 for a patch, 27.1-rc.1
for a release candidate.

- VERSION names the release main is working towards. The commit tagged
  inbuxa-v<VERSION> reports it bare; every other build adds +pr<N> or
  +g<sha>, so a build between releases never passes for the release.
- Gitea's merge subject ("Merge pull request 'Title' (#76) from ...") is
  now recognised. The dated scheme only knew GitHub's form, so every
  Gitea merge went out as +g<sha>.
- CI publishes a release candidate as a pre-release, tagged 27.1-rc.N and
  27.1-rc, never latest; a release moves its own tag, its series and
  latest (scripts/release-version.sh, the console's helper). The GHCR
  copy follows the same tags.
- deploy.example.sh does the same sum in shell, and still names a pre-27.1
  tree by its date, so a rollback reports what it reported then.
- About explains the new form; the text is retranslated in all ten
  catalogs.

Claude-Session: https://claude.ai/code/session_01Y2F7CWRXorttf5sjSbxwpj
2026-10-28 09:46:10 -07:00

7 lines
396 B
TypeScript

/** Types for `version.mjs`, which is plain JS so the Dockerfile and shell can run it directly. */
export const UNVERSIONED: string;
export function readRelease(): string;
export function formatVersion(commit: { release: string; tagged?: boolean; subject?: string; sha: string }): string;
export function versionFromGit(release?: string): string | null;
export function resolveVersion(): string;