Aliaksandr Valialkin
0ad48a7ea8
Add exclude google.golang.org/grpc/stats/opentelemetry v0.0.0-20240907200651-3ffb98b2c93a to go.mod according to https://github.com/googleapis/google-cloud-go/issues/11283#issuecomment-2558515586 . This fixes the following strange issue on `make vendor-update`: cloud.google.com/go/storage imports google.golang.org/grpc/stats/opentelemetry: ambiguous import: found package google.golang.org/grpc/stats/opentelemetry in multiple modules: google.golang.org/grpc v1.69.0 (/go/pkg/mod/google.golang.org/[email protected].0/stats/opentelemetry) google.golang.org/grpc/stats/opentelemetry v0.0.0-20240907200651-3ffb98b2c93a (/go/pkg/mod/google.golang.org/grpc/stats/[email protected])
1.3 KiB
Releases
What to do know before cutting a release
While prometheus/sigv4 does not have a formal release process. We strongly encourage you follow these steps:
- Scan the list of available issues / PRs and make sure that You attempt to merge any pull requests that appear to be ready or almost ready
- Notify the maintainers listed as part of
MANTAINERS.mdthat you're going to do a release.
With those steps done, you can proceed to cut a release.
How to cut an individual release
There is no automated process for cutting a release in prometheus/sigv4. A manual release using GitHub's release feature via this link is the best way to go. The tag name must be prefixed with a v e.g. v0.53.0 and then you can use the "Generate release notes" button to generate the release note automagically ✨. No need to create a discussion or mark it a pre-release, please do mark it as the latest release if needed.
Versioning strategy
We aim to adhere to Semantic Versioning as much as possible. For example, patch version (e.g. v0.0.x) releases should contain bugfixes only and any sort of major or minor version bump should be a minor or major release respectively.