Skip to content

Added tips on releasing client and checking with k8s. #1723

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 27, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,16 @@ We use [Semantic Versioning](https://semver.org/).
- Click "Publish release"!
- Create PR against [prometheus/prometheus](https://github.com/prometheus/prometheus) using RC version (e.g. https://github.com/prometheus/prometheus/pull/15851)
- Create PR against [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes) using RC version (e.g. https://github.com/kubernetes/kubernetes/pull/129752)
- Kubernetes uses scripts to update deps e.g.:

```bash
./hack/pin-dependency.sh github.com/prometheus/client_golang v1.21.0-rc.0
./hack/update-vendor.sh
# If indirect dependencies changed, following check will fail on the CI:
./hack/verify-vendor.sh
# You will need to modify hack/unwanted-dependencies.json manually as the check suggests.
```

- Make sure the CI is green for the PRs
- Allow 1-2 days for downstream testing
- Fix any issues found before final release
Expand Down
Loading