Skip to content
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

Merged
merged 1 commit into from
Jun 21, 2024

Conversation

dimitarvdimitrov
Copy link
Contributor

What this PR does

This cuts the changelog as of r295.

related to #8390

Checklist

  • Tests updated.
  • Documentation added.
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
  • about-versioning.md updated with experimental features.

* [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
Copy link
Contributor Author

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

@dimitarvdimitrov dimitarvdimitrov mentioned this pull request Jun 21, 2024
66 tasks
@dimitarvdimitrov dimitarvdimitrov added the release Release process label Jun 21, 2024
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
@pstibrany
Copy link
Member

it's friday, there will be new weekly r296 on monday, perhaps we can create 2.13 from that branch instead?

@dimitarvdimitrov
Copy link
Contributor Author

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 unreleased section. The same is also visible in this diff

git diff origin/r295 origin/dimitar/2.13/tidy-up-changelog -- CHANGELOG.md

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
This cuts the changelog as of r295

Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
@dimitarvdimitrov dimitarvdimitrov force-pushed the dimitar/2.13/tidy-up-changelog branch from a8d4d26 to f44396c Compare June 21, 2024 13:21
@dimitarvdimitrov dimitarvdimitrov enabled auto-merge (squash) June 21, 2024 13:26
@dimitarvdimitrov dimitarvdimitrov merged commit 05c711d into main Jun 21, 2024
29 checks passed
@dimitarvdimitrov dimitarvdimitrov deleted the dimitar/2.13/tidy-up-changelog branch June 21, 2024 13:33
@grafanabot
Copy link
Contributor

The backport to release-2.13 failed:

The process '/usr/bin/git' failed with exit code 1

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 base branch is release-2.13 and the compare/head branch is backport-8459-to-release-2.13.

dimitarvdimitrov added a commit that referenced this pull request Jun 21, 2024
This cuts the changelog as of r295

Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
(cherry picked from commit 05c711d)
dimitarvdimitrov added a commit that referenced this pull request Jun 21, 2024
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants