AJ ONeal c4a31cbee8
feat(monorel/release): write+commit .goreleaser.yaml and auto-tag patch
monorel release now mirrors the init lifecycle for the goreleaser config:

1. Write .goreleaser.yaml (always regenerate; warn on stock {{ .ProjectName }})
2. git add + commit it if the file changed
3. Auto-tag patch — but only if the yaml commit is the sole new commit
   since the last stable tag (same heuristic as monorel init).
   If there are >1 new commits, print a note and skip auto-tag so the
   user can choose the right semver component with monorel bump.
4. Compute version info *after* the yaml commit and auto-tag, so the
   generated script reflects the tag that was just created.
2026-03-01 19:13:50 -07:00
2021-03-10 16:58:54 -07:00
2026-03-01 00:18:32 -07:00
2026-02-12 00:38:04 -07:00
2025-10-11 19:03:58 -06:00

golib

Go Reference

Sometimes a little copying, sometimes a little dependency. Too small for their own repos.

The default branch is dev, but the stable, versioned tags are based on main.

Also, my Go Cheatsheet:

Description
Sometimes a little copying, sometimes a little dependency, but too small for their own repos.
Readme MPL-2.0 16 MiB
Languages
Go 100%