Replace the generic ci.yml jobs with the shared go-pr and go-release workflows.
Add autoupdate through shared go-autoupdate.
Keep golangci-lint in a separate lint.yaml, because the shared workflows do not run it.
Add a build-less .goreleaser.yaml so the shared release flow can tag and publish the library.
First CI run failed because:
- staticcheck v0.7.0, gosec, govulncheck (all @latest) require Go >= 1.25
- golangci-lint-action v6 does not support golangci-lint v2
Aligns Go version with the rest of the consumer projects (go-telegram,
mcp-filepuff, kportal, lolcathost all on 1.25.x).
Replicates the standard CI + release process from go-telegram:
- vet, staticcheck, govulncheck, gosec, golangci-lint, race-tested test
on every push and PR
- ci-success aggregator as the single required status check
- release job auto-fires on clean push to main: lukaszraczylo/semver-generator
computes next version from commit history, tags v<X.Y.Z>, and
`gh release create --generate-notes` publishes a GitHub release
oss-telemetry is library-only, so unlike go-telegram there is no
GoReleaser step and no binaries are attached — consumers continue to
go get github.com/lukaszraczylo/oss-telemetry@<tag>.
.semver.yaml mirrors the keyword set used in go-telegram (Conventional
Commits prefixes, BREAKING CHANGE for major).
lukaszraczylo
