Maven Release Validation

Turn a Maven release request into an evidence-backed checklist. Treat source verification, Git synchronization, repository publication, clean-cache consumption, CI, and runtime readiness as separate gates. Never infer a later gate from an earlier one.

Quick start

Typical requests:

• “用 $maven-release-validation 验证三个维护分支能否发布到阿里云 Maven。”
• “审计这次 SNAPSHOT 发布，确认 GitHub、Codeup 和远端构件一致。”
• “为下游项目做空缓存消费验证，并给出可复核的发布报告。”

Start by discovering the real repository/worktree, current branch, dirty state, wrapper, POM hierarchy, repository configuration, and existing release scripts. If .codegraph/ exists, use CodeGraph before text search for code-structure questions. Do not create/switch branches, commit, push, deploy, delete caches, or modify repository settings unless the user requested that mutation.

Inputs and release matrix

Build a matrix before executing: