gradle-wrapper-upgrade
Gradle Wrapper Upgrade
Two modes — match the user's verb
Decide this first; everything below is conditional on it.
- "Upgrade the wrapper", "bump Gradle to 8.14.4" → act: work the steps, verify, report.
- "How do I upgrade the wrapper?" → give the commands, name the run-it-twice gotcha, stop. A "how" question is answered, not executed — including when you have already opened with "I'll upgrade the wrapper." Say the commands; do not run them.
If genuinely ambiguous, give the commands.
The steps below are the same material either way: in act mode you run them, in answer mode you hand them over.
Upgrading means running the built-in wrapper task, never hand-editing files: gradlew, gradlew.bat, and gradle-wrapper.jar are generated, and the next wrapper run reverts any edit without warning. Scope: a wrapper that already exists — adding one to a project with none is a different job (gradle :wrapper from a system Gradle install).
Two references ship beside this file, for branches most upgrades never hit: references/snapshot.md (Step 3 — securing the wrapper where git cannot) and references/rollback.md (Step 6 — undoing an upgrade the build cannot take). Open either only when the step says to.