
The service is shipped as a Docker image in the GitHub Container Registry (ghcr.io), built from
the oidf-services module with jib. Two workflows publish it, and neither one changes the Maven
version: the version in the POMs is what the image is tagged with.
Every push to main triggers
docker-snapshot.yml, which publishes an image
tagged with the version in the POMs, for example 0.11.16-SNAPSHOT.
When main holds a release version (no -SNAPSHOT suffix), nothing is published, so a release
image is never overwritten by a later commit.
To publish a versioned release image:
Set the release version in the POMs, e.g. 0.11.16, and commit it:
mvn versions:set -DnewVersion=0.11.16 -DprocessAllModules=true -DgenerateBackupPoms=false
Push an annotated git tag named v followed by that version:
git tag -a v0.11.16 -m "Version 0.11.16"
git push origin v0.11.16
Set the next snapshot version in the POMs, e.g. 0.11.17-SNAPSHOT.
In practice all three steps are driven by internal/release.sh, see
internal/release.md.
Pushing a tag of the form v* triggers
docker-release.yml, which:
v0.11.16 ↔ 0.11.16) and that the
version is not a snapshot. If either check fails, the workflow fails and nothing is published.ghcr.io tagged with the version and with
latest.The same tag also triggers github-release.yml,
which creates a GitHub release pointing at the release notes. It builds nothing and attaches no
assets.
The tag name must start with v. Tags that do not match this pattern trigger neither workflow.
mvn clean compile jib:dockerBuild@local -Djib.from.platforms=linux/amd64
Use linux/arm64 instead for an ARM image. The local build tags the image local/oidf-services
and pushes nothing.
Copyright © 2024-2026, Sweden Connect. Licensed under version 2.0 of the Apache License.