Upgrade the project to a new Godot patch release (e.g. 4.6.0 to 4.6.1). Use when bumping the Godot patch version.
Upgrade this project to Godot patch version $ARGUMENTS. Only 2 files are modified during
a patch upgrade — README.md and package-addon/action.yaml. No other files change because
Docker image tags and workflow variables use major.minor only.
Validate the argument. Extract the full version (e.g. 4.6.1) from $ARGUMENTS. Strip
a leading v if present. Verify the format is major.minor.patch where patch > 0. If
invalid, stop and ask the user.
Read the target files to determine the current version and find the exact strings to replace:
README.md — find the Shields.io badge URL containing godot-v<VERSION> and the version
table entry under #### Release tag: Godot versionpackage-addon/action.yaml — find the godot-editor-version input's default valueVerify this is an upgrade: the new version's must match the current entry's , and the new patch must be higher than the current patch (or current patch must be 0). If not, stop and ask the user.
major.minormainmajor.minorUpdate README.md — exactly two edits:
https://img.shields.io/badge/godot-v<OLD>-478cbf →
https://img.shields.io/badge/godot-v<NEW>-478cbfmain mapping entry
e.g. `v4.6.0` → `v4.6.1`Update package-addon/action.yaml — one edit:
godot-editor-version default: Replace the default value
e.g. "v4.6-stable" or "v4.6.0-stable" → "v4.6.1-stable"Verify the diff. Run git diff --stat and confirm exactly 2 files changed with 3
insertions and 3 deletions.
Commit with the message:
chore: upgrade to Godot `v<NEW_VERSION>-stable`
README.md — badge (line 1) and version tablepackage-addon/action.yaml — godot-editor-version default valuev4.4 → v4.4.1: commit b379589 (PR #375)v4.5 → v4.5.1: commit 02b5552 (PR #452)