[release-v3.0] Fix page weights in release notes - #7336
Merged
Conversation
(cherry picked from commit 74d5997) Co-authored-by: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com>
tempo-ci-app
Bot
requested review from
electron0zero,
ie-pham,
javiermolinar,
knylander-grafana,
mapno,
mdisibio,
stoewer,
yvrhdn and
zalegrala
as code owners
June 1, 2026 14:40
tempo-ci-app
Bot
added
type/docs
tempo-ci-app
Bot
requested review from
carles-grafana,
mattdurham,
oleg-kozlyuk-grafana and
ruslan-mikhailov
as code owners
June 1, 2026 14:40
knylander-grafana
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport 74d5997 from #7335 job run
What this PR does:
Fixes the page weights in the release notes folder so the 3.0 release notes are at the top instead of the bottom.
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]