.github/workflows/release.yml, run on the private GitHub mirror (github.com/inbuxa/inbuxa-charts, push-mirrored from here) for GitHub's OIDC identity, like the image signing.
A tag v27.1-rc.N → chart 27.1.0-rc.N:
Images:release/suite.yaml names the server, webmail and console tags. Each image's signature is checked against its own repository's sign.yml, then its digest is pinned into values.yaml with the tag (tools/release-stamp.py, which touches only those lines and refuses a server from another series).
Chart: linted against every ci/ values file, packaged, pushed to oci://ghcr.io/inbuxa/charts and oci://registry.coffeylabs.org/inbuxa/charts, signed keyless with cosign by digest, and verified.
Rendered manifests from ci/defaults-values.yaml, with that values file and a README, for applying without Helm.
SHA256SUMS over the chart and the tarball, signed with the inbuxa release key (minisign).
Gitea release with the files and the pinned digests.
verify: a fresh runner runs tools/verify-release.sh with only what was published.
Run by hand from main, it makes a test release 0.0.0-test.N pushed to oci://ghcr.io/inbuxa/charts-test, with no release page; SHA256SUMS is signed only if the key is there. Real releases from a tag fail without GITEA_TOKEN and MINISIGN_SECRET_KEY.
Checked locally: stamping, lint, package and render against rc.33 / webmail rc.10 / console rc.22 (17 objects; all three digests pinned and read back by the verify script's parser), tag ↔ version mapping both ways, bash -n on every step, tools/check.sh.
After merge: dispatch a test release on GitHub as the end-to-end run.
Closes #13.
`.github/workflows/release.yml`, run on the private GitHub mirror (github.com/inbuxa/inbuxa-charts, push-mirrored from here) for GitHub's OIDC identity, like the image signing.
A tag `v27.1-rc.N` → chart `27.1.0-rc.N`:
1. **Images:** `release/suite.yaml` names the server, webmail and console tags. Each image's signature is checked against its own repository's `sign.yml`, then its digest is pinned into `values.yaml` with the tag (`tools/release-stamp.py`, which touches only those lines and refuses a server from another series).
2. **Chart:** linted against every `ci/` values file, packaged, pushed to `oci://ghcr.io/inbuxa/charts` and `oci://registry.coffeylabs.org/inbuxa/charts`, signed keyless with cosign by digest, and verified.
3. **Rendered manifests** from `ci/defaults-values.yaml`, with that values file and a README, for applying without Helm.
4. **SHA256SUMS** over the chart and the tarball, signed with the inbuxa release key (minisign).
5. **Gitea release** with the files and the pinned digests.
6. **verify**: a fresh runner runs `tools/verify-release.sh` with only what was published.
Run by hand from main, it makes a test release `0.0.0-test.N` pushed to `oci://ghcr.io/inbuxa/charts-test`, with no release page; SHA256SUMS is signed only if the key is there. Real releases from a tag fail without `GITEA_TOKEN` and `MINISIGN_SECRET_KEY`.
Checked locally: stamping, lint, package and render against rc.33 / webmail rc.10 / console rc.22 (17 objects; all three digests pinned and read back by the verify script's parser), tag ↔ version mapping both ways, `bash -n` on every step, `tools/check.sh`.
After merge: dispatch a test release on GitHub as the end-to-end run.
.github/workflows/release.yml runs on the GitHub mirror, for the keyless
identity the images are signed with. A tag v27.1-rc.N releases chart
27.1.0-rc.N: the images in release/suite.yaml are checked against the
workflows that signed them and pinned by digest (tools/release-stamp.py);
the chart is linted, packaged, pushed to GHCR and the Gitea registry and
signed with cosign; manifests rendered from ci/defaults-values.yaml and
SHA256SUMS (minisign) go on the Gitea release. A verify job then runs
tools/verify-release.sh on a fresh runner, as someone installing would.
Run by hand from main it makes a test release, 0.0.0-test.N, pushed to
charts-test with no release page.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #13.
.github/workflows/release.yml, run on the private GitHub mirror (github.com/inbuxa/inbuxa-charts, push-mirrored from here) for GitHub's OIDC identity, like the image signing.A tag
v27.1-rc.N→ chart27.1.0-rc.N:release/suite.yamlnames the server, webmail and console tags. Each image's signature is checked against its own repository'ssign.yml, then its digest is pinned intovalues.yamlwith the tag (tools/release-stamp.py, which touches only those lines and refuses a server from another series).ci/values file, packaged, pushed tooci://ghcr.io/inbuxa/chartsandoci://registry.coffeylabs.org/inbuxa/charts, signed keyless with cosign by digest, and verified.ci/defaults-values.yaml, with that values file and a README, for applying without Helm.tools/verify-release.shwith only what was published.Run by hand from main, it makes a test release
0.0.0-test.Npushed tooci://ghcr.io/inbuxa/charts-test, with no release page; SHA256SUMS is signed only if the key is there. Real releases from a tag fail withoutGITEA_TOKENandMINISIGN_SECRET_KEY.Checked locally: stamping, lint, package and render against rc.33 / webmail rc.10 / console rc.22 (17 objects; all three digests pinned and read back by the verify script's parser), tag ↔ version mapping both ways,
bash -non every step,tools/check.sh.After merge: dispatch a test release on GitHub as the end-to-end run.