mirror of
https://github.com/lukaszraczylo/oss-telemetry.git
synced 2026-10-12 00:45:30 +00:00
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).
43 lines
1.2 KiB
YAML
43 lines
1.2 KiB
YAML
# Configuration for lukaszraczylo/semver-generator.
|
|
# Reference: https://github.com/lukaszraczylo/semver-generator
|
|
#
|
|
# Word matching is fuzzy + case-insensitive. The keywords below mirror the
|
|
# Conventional Commits prefixes used in this repo's git history. Same pattern
|
|
# as github.com/lukaszraczylo/go-telegram/.semver.yaml.
|
|
|
|
version: 1
|
|
|
|
# Respect existing v* tags as the version baseline. semver-generator finds
|
|
# the highest existing tag and bumps from there. With no tags yet, the first
|
|
# release computes from the empty base.
|
|
force:
|
|
existing: true
|
|
|
|
# Skip merge commits and machine-generated traffic that would otherwise
|
|
# spuriously bump the version.
|
|
blacklist:
|
|
- "Merge branch"
|
|
- "Merge pull request"
|
|
- "Merge remote-tracking branch"
|
|
- "go mod tidy"
|
|
|
|
wording:
|
|
patch:
|
|
- "fix"
|
|
- "chore"
|
|
- "docs"
|
|
- "test"
|
|
- "style"
|
|
- "refactor"
|
|
- "build"
|
|
- "ci"
|
|
- "perf"
|
|
minor:
|
|
- "feat"
|
|
major:
|
|
# Match only the canonical Conventional Commits trailer. The bare word
|
|
# "breaking" is too greedy under semver-generator's fuzzy match — it
|
|
# triggers on substrings inside a commit body and wrongly produces a
|
|
# major bump.
|
|
- "BREAKING CHANGE"
|