Release Checklist

Release Checklist

CraftLedger Jobs is not ready for a first public jar release until this checklist passes.

Code

• ./gradlew build passes.
• For each non-primary target jar, ./gradlew build -Pcraftledger_mc_target=<profile> passes.
• The Release Build workflow passes for every target intended for release.
• CI passes on main.
• No known balance duplication bugs.
• No known permission bypasses.
• Config reload behavior is tested.
• Data persistence survives server restart.

Server Compatibility

• Dedicated Forge 1.20.1 / Forge 47.4.10 server boots.
• Each non-primary target jar has equivalent dedicated-server staging evidence before it is published.
• A client without CraftLedger Jobs can join.
• No rejected mod channel/version error appears.
• No client-side install is required.

Documentation

• README is current.
• Commands are documented.
• Config examples are documented.
• Installation/admin docs are documented.
• Wiki pages are current.
• Repository social preview is set from .github/assets/social-preview.png.
• Changelog entry is written.
• Known limitations are documented.

Publishing

• Version number is updated.
• A v* tag release build has produced reviewed workflow artifacts.
• GitHub release notes are written.
• Release jar is attached to GitHub release.
• CurseForge description and project metadata are ready.
• Repository variable CURSEFORGE_PROJECT_ID is set.
• Repository secret CURSEFORGE_TOKEN is set.
• The curseforge GitHub Actions environment is protected by required reviewers.
• CurseForge Publish is run manually only after staging evidence is complete.