# Release process

Use the shared QRun release pipeline, delegated through `.gitea/workflows/qrun-release.yaml` to the protected `qrun-release-v1` channel. Repository CI and publisher enrollment must be enabled before publication; no signing or registry credentials belong in this repository.

- `develop` builds snapshots; `release/*` builds release candidates; stable `vX.Y.Z` tags publish stable artifacts.
- The shared pipeline computes the effective Maven revision, tests it, retains the JAR/source/Javadoc/POM, and passes the verified artifacts to the trusted publisher.
- Confirm CI and publication before announcing an artifact. Check Maven Central from a clean consumer and record the matching Next frontend release that supports `QQQ_TOOLS`.
- First release target: `com.kingsrook.qbits:qbit-tools:0.1.0`. This target is not a publication receipt.
- Requires Java 21 and QQQ 4.1.0-RC.21. The compatible Next implementation is tracked in https://git.kof22.com/QRun-IO/qqq-frontend-next/pulls/204; do not claim older released frontends support it.
- No database migration or background service is installed. Roll back by removing the Tools producer/dependency or returning to the previous frontend; existing companion clients and device records are unaffected.
- Bundled scripts pin Print Client 1.0.1 and signed scanner preview 1.0.0. They have syntax and UI copy checks, but real OS/device installation qualification remains outstanding. Scanner preview is explicitly labeled and requires forge login.