Historic AtlasRELEASE ENGINEERING ↘
KNOWN SOURCE. NAMED VERSION.

Ship a release.
Not a guess.

An annotated tag, a clean tree and a consistent set of images. A field guide to making the atlas reproducible.

LOCAL POLICY EXPLORER · NO COMMANDS EXECUTED
ANNOTATED GIT TAG / SPECIMEN
v0.2.0
on main · sample commit a1b2c3d
notes = commit subjects since prior release
signature = configured signing key, if any
01 / PREPARECheck the source

Clean, main, remote in sync, work items valid.

02 / NAMETag with notes

Semantic version greater than the last release.

03 / PUBLISHBuild four modules

Release workflow publishes one consistent set.

04 / RUNChoose the release

Host checks out the tag or selects published tags.

THE RELEASE CONTRACT

Make the guardrails
visible.

Try the preflight with sample repository conditions. Versions compare numerically, not alphabetically. First release: 0.1.0; while major is zero, breaking changes raise minor.

This page does not inspect your repository. It previews tools/release.sh behavior; no tag or push is made.

SAME SOURCE, DIFFERENT EVENTS

Publish only
what the event means.

Each module workflow calls build-module.yml. Pull requests only build; main pushes publish changed modules; release tags build all four.

Repository namespace: ghcr.io/avarcorg. Images are public; hosts can pull without a registry login. POM versions tag local builds, not the published release names.

Main-push notification is best effort, after successful publish, same repository only. PRs, forks and releases do not notify. A deployment-side listener treats a message only as a hint and checks the registry. Automatic host deployment is not defined here.

CLEAN HISTORY, KEEP RELEASES

Retention is a rule.
Not a blanket delete.

Inspect a single synthetic image version. Weekly/on-demand cleanup protects release tags, snapshot, latest, and the newest five versions.

Policy-only preview; no registry is contacted. The actual workflow uses packages:write and supports dry run and retention inputs. Hosts select snapshot or release tags, never bare sha tags.

Notes live with the tag.

Each annotated tag message lists commit subjects since the previous release, one per line, including source work-item references. No separate changelog. If a signing key is configured, git tag -s signs it; otherwise it is annotated only.

Runs are not releases.

Workflow-run cleanup is separate: finished runs older than 30 days, preserving the newest five of each workflow. Queued and running runs stay. Permission: actions:write. Images, git tags and releases are unaffected.

Builds have boundaries.

Java/Node versions in the reusable workflow must match the POMs. Maven/wrapper/npm downloads are cached; pulled Docker images and pack-internal downloads are not. Stage uses snapshot; production uses release tags only when it exists.

All versions, conditions and command outputs above are specimens. This page does not create releases, publish images, remove packages, contact webhooks or deploy services.