Number the webmail with the suite: 27.1-rc.1 #77

Merged
jcoffey-dev merged 1 commits from release/version-27.1-rc.1 into main 2026-10-28 16:52:53 +00:00
Owner

Moves the webmail to the suite's release numbers for the 27.1 rc.1 gate: 27.1 for a series, 27.1.3 for a patch, 27.1-rc.1 for a release candidate. Until now it used dated versions like 2026.10.26+gcff6f1f.

  • 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 can't pass for the release.
  • Gitea's merge subject (Merge pull request 'Title' (#76) from …) is now matched. The old pattern only knew GitHub's form, so every Gitea merge shipped as +g<sha>.
  • CI publishes an RC as a pre-release, tagged 27.1-rc.N and 27.1-rc, and never moves latest. A release moves its own tag, its series and latest. GHCR gets the same tags. scripts/release-version.sh is the console's helper, and its test runs in CI.
  • The tag check now compares the tag with VERSION, and version.mjs has to agree.
  • deploy.example.sh does the same calculation in shell. A rollback to a tree from before 27.1 is still named by its date.
  • The About text explaining the version is rewritten. Translation: I retranslated it in all ten catalogs (de, es, fr, ja, nl, pt-BR, ru, tr, uk, zh-Hans). i18n:check reports 100%.

Checks run locally: typecheck, npm test (283 pass), i18n:check, build, and release-version.test.sh under sh and busybox. Tagged, untagged, Gitea and GitHub merge commits, an invalid VERSION, and a rollback to inbuxa-v2026.10.26-gcff6f1f were each checked in a scratch clone.

No tag is pushed here. inbuxa-v27.1-rc.1 waits until the whole suite is on the same number.

Moves the webmail to the suite's release numbers for the 27.1 rc.1 gate: `27.1` for a series, `27.1.3` for a patch, `27.1-rc.1` for a release candidate. Until now it used dated versions like `2026.10.26+gcff6f1f`. - `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 can't pass for the release. - Gitea's merge subject (`Merge pull request 'Title' (#76) from …`) is now matched. The old pattern only knew GitHub's form, so every Gitea merge shipped as `+g<sha>`. - CI publishes an RC as a pre-release, tagged `27.1-rc.N` and `27.1-rc`, and never moves `latest`. A release moves its own tag, its series and `latest`. GHCR gets the same tags. `scripts/release-version.sh` is the console's helper, and its test runs in CI. - The tag check now compares the tag with `VERSION`, and `version.mjs` has to agree. - `deploy.example.sh` does the same calculation in shell. A rollback to a tree from before 27.1 is still named by its date. - The About text explaining the version is rewritten. **Translation:** I retranslated it in all ten catalogs (de, es, fr, ja, nl, pt-BR, ru, tr, uk, zh-Hans). `i18n:check` reports 100%. Checks run locally: typecheck, `npm test` (283 pass), `i18n:check`, build, and `release-version.test.sh` under sh and busybox. Tagged, untagged, Gitea and GitHub merge commits, an invalid `VERSION`, and a rollback to `inbuxa-v2026.10.26-gcff6f1f` were each checked in a scratch clone. No tag is pushed here. `inbuxa-v27.1-rc.1` waits until the whole suite is on the same number.
jcoffey-dev added 1 commit 2026-10-28 16:46:40 +00:00
Number the webmail with the suite: 27.1-rc.1
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
76ee66f106
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
jcoffey-dev merged commit 4e1b5d76d2 into main 2026-10-28 16:52:53 +00:00
jcoffey-dev deleted branch release/version-27.1-rc.1 2026-10-28 16:52:54 +00:00
Sign in to join this conversation.