ci: rebuild from templates on the docker base with release plumbing #21

Merged

gravityfargo merged 2 commits from chore/template-rebuild into main

2026-08-02 00:03:44 +00:00

gravityfargo commented

2026-08-01 23:50:56 +00:00

Owner

First adoption of the templates repo (templates@3028942). Every template-owned file was deleted and re-applied from the layers; nothing else was touched.

Layers applied

common — shared floor
docker — base type, detected from the Dockerfile marker
common-versioning + common-versioning-docker — release plumbing
no documentation publisher
baseline build/publish pair (no docker-multiarch / docker-simple)

Not touched

Dockerfile, bump.yml, cz-preview, entrypoint.sh, CHANGELOG.md. The Dockerfile is real, so the layer's baseline was not applied over it; bump.yml is this repo's product.

Carried-forward divergences

Three files deviate from the layers as shipped, all reported as legit patches rather than silently normalised:

.dockerignore — baseline * + !Dockerfile plus !entrypoint.sh and !cz-preview. The image COPYs both; the baseline alone makes them invisible to the build. CI confirms the image builds with this form.
build-version.yml — uses: ./.forgejo/workflows/bump.yml instead of the layer's ModernLeft/commitizen-ci/.forgejo/workflows/bump.yml@0.3.0. This is that repo; the pinned form would make it release through its own previous tag rather than its working copy.
README.md — kept, where the common layer ships it empty. It is the fleet's only written record of the CZ_SIGNING_KEY setup, the per-repo bump.yml adoption snippet, and the /commitizen-bot Infisical path. Restored in 7693de9, with the one pr-bump-preview.yaml → .yml reference this rebuild's rename invalidated.

What changed in behaviour

runs-on moves from docker to ubuntu-latest (workflows) and modernleft-general-ci (code quality).
Docker layer caching moves from actions/cache on ${{ runner.temp }}/.buildx-cache to type=gha.
Buildx gains network=forgejo-runner-network and memory=3g driver opts.
Infisical domain moves from the literal URL to ${{ vars.INFISICAL_DOMAIN }}.
The inline test-build job splits into reusable test-build.yml + code-quality.yml.
Workflow filenames normalise from .yaml to .yml; .cz.toml becomes cz.toml; renovate.json moves to .forgejo/renovate.json.

CI

Green on 5314f52: run 4227 (test-build.yml — build, checks, code-quality) and run 4226 (pr-bump-preview.yml). The bump preview comment confirms no commit here is bump-eligible, so merging cannot cut a release.

Unproven by this PR, because a pull request cannot meet their triggers: build-version.yml (push to main), publish.yml (tag push), bump.yml (workflow_call), and the ${{ vars.INFISICAL_DOMAIN }} substitution. Those first execute on merge.

Known-stale, pre-existing

README.md points at .forgejo/workflows/build-push.yaml, which does not exist under any name and did not before this rebuild either. Left alone rather than fixed here.

Committed with inert types throughout.

First adoption of the templates repo (`templates@3028942`). Every template-owned file was deleted and re-applied from the layers; nothing else was touched. ## Layers applied - `common` — shared floor - `docker` — base type, detected from the `Dockerfile` marker - `common-versioning` + `common-versioning-docker` — release plumbing - no documentation publisher - baseline build/publish pair (no `docker-multiarch` / `docker-simple`) ## Not touched `Dockerfile`, `bump.yml`, `cz-preview`, `entrypoint.sh`, `CHANGELOG.md`. The `Dockerfile` is real, so the layer's baseline was not applied over it; `bump.yml` is this repo's product. ## Carried-forward divergences Three files deviate from the layers as shipped, all reported as legit patches rather than silently normalised: - **`.dockerignore`** — baseline `*` + `!Dockerfile` plus `!entrypoint.sh` and `!cz-preview`. The image `COPY`s both; the baseline alone makes them invisible to the build. CI confirms the image builds with this form. - **`build-version.yml`** — `uses: ./.forgejo/workflows/bump.yml` instead of the layer's `ModernLeft/commitizen-ci/.forgejo/workflows/bump.yml@0.3.0`. This is that repo; the pinned form would make it release through its own previous tag rather than its working copy. - **`README.md`** — kept, where the `common` layer ships it empty. It is the fleet's only written record of the `CZ_SIGNING_KEY` setup, the per-repo `bump.yml` adoption snippet, and the `/commitizen-bot` Infisical path. Restored in `7693de9`, with the one `pr-bump-preview.yaml` → `.yml` reference this rebuild's rename invalidated. ## What changed in behaviour - `runs-on` moves from `docker` to `ubuntu-latest` (workflows) and `modernleft-general-ci` (code quality). - Docker layer caching moves from `actions/cache` on `${{ runner.temp }}/.buildx-cache` to `type=gha`. - Buildx gains `network=forgejo-runner-network` and `memory=3g` driver opts. - Infisical `domain` moves from the literal URL to `${{ vars.INFISICAL_DOMAIN }}`. - The inline test-build job splits into reusable `test-build.yml` + `code-quality.yml`. - Workflow filenames normalise from `.yaml` to `.yml`; `.cz.toml` becomes `cz.toml`; `renovate.json` moves to `.forgejo/renovate.json`. ## CI Green on `5314f52`: run 4227 (`test-build.yml` — build, `checks`, `code-quality`) and run 4226 (`pr-bump-preview.yml`). The bump preview comment confirms no commit here is bump-eligible, so merging cannot cut a release. Unproven by this PR, because a pull request cannot meet their triggers: `build-version.yml` (push to `main`), `publish.yml` (tag push), `bump.yml` (`workflow_call`), and the `${{ vars.INFISICAL_DOMAIN }}` substitution. Those first execute on merge. ## Known-stale, pre-existing `README.md` points at `.forgejo/workflows/build-push.yaml`, which does not exist under any name and did not before this rebuild either. Left alone rather than fixed here. Committed with inert types throughout.

gravityfargo added 1 commit

2026-08-01 23:50:57 +00:00

ci: rebuild from templates on the docker base with release plumbing

PR Bump Preview / Preview version bump (pull_request) Successful in 7s

Details

Test Build / Test build image (pull_request) Successful in 1m1s

Details

Test Build / checks (pull_request) Successful in 6s

Details

Test Build / code-quality (pull_request) Successful in 0s

Details

5314f5246c