release: ci-base 1.0.0 #3

Merged
crapougnax merged 5 commits from develop into main 2026-11-14 11:44:58 +00:00
Member

First stable release of the repository.

Content

  • images/ci-base 1.0.0: job image for Forgejo Actions runners (Node.js 22 with Corepack, Bun, Git LFS, build toolchain, Docker CLI with Buildx, PostgreSQL client), unprivileged by default.
  • actions/build-image: builds a recipe, runs its smoke test and publishes it for amd64 and arm64.
  • .forgejo/workflows/publish.yml: publication from the fork of a forge, idle while the variable IMAGE_REGISTRY is not set.

Verified

  • CI of this repository green on pull request and on develop.
  • A configured fork published the develop channel for amd64 and arm64.
  • A monorepo CI ran on the published image as the unprivileged user: 844 tests green.

Not exercised yet: the release channel (tags X.Y.Z, X.Y, X). Its first run is the one this release triggers on a fork.

After the merge

  1. Tag main with an annotated SemVer tag.
  2. Synchronise the main branch of each fork: it publishes 1.0.0, 1.0 and 1.

Merge with a merge commit, not a squash, so that develop and main keep a common history.

🤖 Generated with Claude Code

First stable release of the repository. ## Content - `images/ci-base` **1.0.0**: job image for Forgejo Actions runners (Node.js 22 with Corepack, Bun, Git LFS, build toolchain, Docker CLI with Buildx, PostgreSQL client), unprivileged by default. - `actions/build-image`: builds a recipe, runs its smoke test and publishes it for amd64 and arm64. - `.forgejo/workflows/publish.yml`: publication from the fork of a forge, idle while the variable `IMAGE_REGISTRY` is not set. ## Verified - CI of this repository green on pull request and on `develop`. - A configured fork published the `develop` channel for amd64 and arm64. - A monorepo CI ran on the published image as the unprivileged user: 844 tests green. Not exercised yet: the release channel (tags `X.Y.Z`, `X.Y`, `X`). Its first run is the one this release triggers on a fork. ## After the merge 1. Tag `main` with an annotated SemVer tag. 2. Synchronise the `main` branch of each fork: it publishes `1.0.0`, `1.0` and `1`. Merge with a merge commit, not a squash, so that `develop` and `main` keep a common history. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat: add the ci-base job image and the build-image action
All checks were successful
CI / Build and test ci-base (pull_request) Successful in 57s
44f3b3a719
ci-base is a job image for Forgejo Actions runners where the usual CI
tools are already installed: Node.js with Corepack, Bun, Git LFS, a
build toolchain, the Docker CLI with Buildx and the PostgreSQL client.
It runs unprivileged and is versioned by the VERSION file next to its
recipe.

The build-image action builds a recipe of the revision it is pinned to,
runs its smoke test and publishes it for amd64 and arm64 to the registry
of the forge that calls it. This repository publishes nothing: its own
workflow only builds and tests, and templates/ci-image.yml is the
workflow a forge copies to build its image.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Reviewed-on: #1
feat: publish from the fork of a forge
Some checks failed
CI / Build and test ci-base (pull_request) Has been cancelled
dad55c54b4
A forge forks this repository and sets the variable IMAGE_REGISTRY and
the registry secrets: the publication workflow then builds the images
and pushes them to the registry of that forge. Without the variable the
workflow does nothing, so the upstream repository never publishes and a
fork carries no change of its own.

The build-image action gains the if-exists input: on the release
channel, 'skip' ends successfully when the version is already published.

The workflow template for a separate repository is removed: the fork
replaces it.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Merge branch 'develop' into feat/ci-base-image
All checks were successful
CI / Build and test ci-base (pull_request) Successful in 1m39s
a794dd946f
Merge pull request 'feat: publish from the fork of a forge' (#2) from feat/ci-base-image into develop
All checks were successful
Publish images / Publish ci-base (push) Successful in 23s
CI / Build and test ci-base (push) Successful in 1m15s
CI / Build and test ci-base (pull_request) Successful in 59s
affb74f4fb
Reviewed-on: #2
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tycho/forge-ci!3
No description provided.