micro--go-micro
Asim Aslam
da5b1a2599
The release action always bumped the PATCH, so genuine features (new providers, `micro loop`, the security role, agent memory, …) all shipped as patches while the minor stayed frozen at .3 (now on v6.3.18). By semver, backward-compatible features are MINOR bumps. Now the bump reflects what shipped, read from the CHANGELOG [Unreleased] section (kept current by the coherence role): - `### Added` / `### Changed` -> MINOR (vX.(M+1).0) - fixes/docs only -> PATCH (vX.M.(P+1)) - breaking (`### Removed` / a "(breaking)" heading / BREAKING) -> skip the automated release; a MAJOR stays a human decision. Applied to both go-micro's loop-release.yml and the generic `micro loop` template (guards a missing CHANGELOG.md -> patch). Verified against the current CHANGELOG: next release resolves to v6.4.0 (features present), not v6.3.19. Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL Co-authored-by: Claude <noreply@anthropic.com>