-
Notifications
You must be signed in to change notification settings - Fork 545
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
2.13 release: tidy up & cut changelog #8459
Conversation
* [FEATURE] Query-frontend, querier: new experimental `/cardinality/active_native_histogram_metrics` API to get active native histogram metric names with statistics about active native histogram buckets. #7982 #7986 #8008 | ||
* [FEATURE] Alertmanager: Added `-alertmanager.max-silences-count` and `-alertmanager.max-silence-size-bytes` to set limits on per tenant silences. Disabled by default. #6898 | ||
* [FEATURE] Alertmanager: Added `-alertmanager.max-silences-count` and `-alertmanager.max-silence-size-bytes` to set limits on per tenant silences. Disabled by default. #8241 #8249 | ||
* [FEATURE] Ingester: add experimental support for the server-side circuit breakers when writing to and reading from ingesters. This can be enabled using `-ingester.push-circuit-breaker.enabled` and `-ingester.read-circuit-breaker.enabled` options. Further `-ingester.push-circuit-breaker.*` and `-ingester.read-circuit-breaker.*` options for configuring circuit-breaker are available. Added metrics `cortex_ingester_circuit_breaker_results_total`, `cortex_ingester_circuit_breaker_transitions_total`, `cortex_ingester_circuit_breaker_current_state` and `cortex_ingester_circuit_breaker_request_timeouts_total`. #8180 #8285 #8315 #8446 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the last PR here still isn't backported to the 2.13 release, but will be once the branch is created, so I'm keeping the changelog entry in the 2.13 section
it's friday, there will be new weekly r296 on monday, perhaps we can create 2.13 from that branch instead? |
I will be taking PTO in the second half of July, so I won't be able to follow-up with anything release-related after July 13th. I also already drafted release notes with r295 in mind. I used this command to verify that everything that's not in r295 is in the new git diff origin/r295 origin/dimitar/2.13/tidy-up-changelog -- CHANGELOG.md |
This cuts the changelog as of r295 Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
a8d4d26
to
f44396c
Compare
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-8459-to-release-2.13 origin/release-2.13
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 05c711d740d8cbcee00d70d495294b31274b2dae
# Push it to GitHub
git push --set-upstream origin backport-8459-to-release-2.13
git switch main
# Remove the local backport branch
git branch -D backport-8459-to-release-2.13 Then, create a pull request where the |
This cuts the changelog as of r295 Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com> (cherry picked from commit 05c711d)
* 2.13 release: tidy up & cut changelog (#8459) This cuts the changelog as of r295 Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com> (cherry picked from commit 05c711d) * Remove unreleased section Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com> --------- Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
What this PR does
This cuts the changelog as of r295.
related to #8390
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.