Description
PR checks and nightly CI should run through the same release workflow used for real releases, so changes to release packaging are validated continuously.
Dry-run / verification runs should:
- exercise release versioning and local tag creation, and verify the resulting version/tag is correct
- not push tags or release commits to the repository
- not publish a GitHub Release or otherwise complete a production release
- still produce installable verification images with distinctive PR/CI tags
- publish those images to a dedicated CI/PR package namespace so the main repository GHCR is unaffected
- retain PR/CI images for only about 1–2 weeks
Real releases remain the only path that publishes production artifacts.
Description
PR checks and nightly CI should run through the same release workflow used for real releases, so changes to release packaging are validated continuously.
Dry-run / verification runs should:
Real releases remain the only path that publishes production artifacts.