Hardened release candidate checklist
This is the local handoff for the first AIV release that supports the hardened composite Action. It does not publish artifacts, create tags, or update remote references.
Release conditions
Before choosing a release version, confirm all of the following from the release commit:
mvn -B -ntp clean verifypasses.java -jar aiv-cli/target/aiv-cli-<version>.jar verify --capabilitiesreturns"status":"ok"and includestrusted-policy.- The same JAR contains
io/github/vaquarkhan/aiv/cli/Main.classand bundled runtime dependencies. -
action.ymldownloads the correct Maven Central coordinate:io/github/vaquarkhan/aiv-cli/<version>/aiv-cli-<version>.jar - The release notes identify the immutable Action commit SHA.
- The GitHub release tag and root
pom.xmluse the identical version. - All source and packaged presets contain the same explicit 18-gate policy.
- The JEV adapter and Terraform validation suites pass.
Required remote operations
These operations are intentionally manual and require explicit authorization:
- Commit the reviewed release candidate.
- Create and push immutable version tag
v<version>. - Verify the GitHub release workflow builds the tag and attaches the shaded CLI JAR.
- Run the Maven Central publish workflow against the same tag using approved publishing credentials.
- Verify the Central JAR download, checksum, CLI version, and capability handshake.
- Update the protected floating major Action reference only after the immutable release works.
- Replace the
<RELEASED_VERSION>and<IMMUTABLE_ACTION_COMMIT_SHA>placeholders in GITHUB-QUICKSTART.md with verified release values.
Do not change a published tag or overwrite a release asset. Publish a follow-up version for fixes.
Post-release smoke test
In a clean sample repository, without Maven or copied AIV source:
- Add the 18-gate starter
.aiv/config.yamlfrom GITHUB-QUICKSTART.md. - Add the workflow using the released JAR version and immutable Action SHA.
- Open a pull request with an objective invariant violation.
- Confirm the required check fails, JSON and SARIF exist, and SARIF appears in code scanning.
- Fix the violation and confirm the check passes.
- If labels are enabled, confirm
aiv:findingsis added and removed idempotently.
This is the success criterion for the first installation milestone: a new repository enables AIV without building Maven or copying AIV source.