release

# Release — Version Bump, Tag, and Changelog Create a new release with a structured changelog and author attribution. ## Arguments - `<version>` — The version to release (e.g. `1.19.1`, `v2.0.0`). The `v` prefix is optional in input but always used for the git tag. If no version is given, detect the current version and suggest the next one (see Step 1). ## Constraints - Only **patch** (`x.y.Z`) or **minor** (`x.Y.0`) bumps. Never bump major — the module path has no `/vN` suffix, so a major bump would violate Go v2+ rules. - All version tags use the `v` prefix (e.g. `v1.20.0`). ## Workflow ### 0. Ensure on main and pull from upstream Verify you are on the `main` branch. If not, stash any pending work and switch: ```bash git branch --show-current ``` If not on `main`: `git stash && git checkout main` Then pull the latest upstream codebase: ```bash git pull upstream main --rebase ``` If there are merge conflicts, resolve them before proceeding. ### 1. Detect current version and suggest the next Read the current version and identify changes since the last tag: 1. Read the code version from `cmd/san/main.go`: ```bash grep 'var version = ' cmd/san/main.go ``` 2. Get the latest git tag: ```bash git describe --tags --abbrev=0 ``` Strip the `v` prefix for comparison. 3. **Compare.** If the code version and tag version differ, warn the user — the code may be out of sync with releases. 4. Get commits since the latest tag: ```bash git log ...