chore: submit semrel to awesome-go under Release Engineering

[mwaldheim]

Goal

Open a PR on awesome-go to list semrel under the Release Engineering or DevOps category.

Requirements (per awesome-go guidelines)

• Project must have a stable release
• README in English
• Proper license
• CI passing

PR text

Name: semrel — A Node.js-free, Go-native semantic release tool with a gRPC plugin architecture and central registry.

[mwaldheim]

Noch nicht umsetzbar: awesome-go verlangt laut CONTRIBUTING.md mindestens 5 Monate Repository-Historie (created_at von SemRels/semrel ist 2026-05-22, also erst ~5-6 Wochen alt). Eine Einreichung würde aktuell mit hoher Sicherheit abgelehnt. Zusätzlich liegt die Testabdeckung einzelner Pakete (internal/cli 48.5%, pkg/git 54.5%) unter der von awesome-go erwarteten Guideline.

Lasse das Issue offen und markiere es als 'blocked' bis (a) die 5-Monats-Schwelle erreicht ist (frühestens ~Ende Oktober 2026) und (b) Testabdeckung der schwächeren Pakete verbessert wurde. Kein Code-Änderungsbedarf jetzt, nur ein Zeit-Blocker.

[mwaldheim]

Blocked: repository age requirement not yet met

Investigated submitting a PR to avelino/awesome-go. Per their CONTRIBUTING.md quick checklist, entries must have at least 5 months of history since the first commit.

semrel's first commit is 2026-05-22. As of today (2026-07-06) that's only ~1.5 months of history — submitting now would very likely be rejected on that basis alone, independent of code quality.

Other requirements are already satisfied and worth noting for when we do submit:

• ✅ Stable SemVer releases (currently v0.24.0)
• ✅ Open source license (Apache-2.0)
• ✅ README in English
• ✅ CI passing
• ⚠️ Still needed at submission time: Go Report Card link, pkg.go.dev doc comments for public APIs, and a coverage report link (per their PR body template) — worth setting these up in the meantime (e.g. wire up goreportcard.com and a coverage badge/report in CI).

Recommendation: revisit this issue on or after 2026-10-22 (5 months from first commit). Leaving open and re-labeling as blocked/future rather than closing, so it isn't lost.