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

Add release notes for v1.5 #3120

Merged
merged 5 commits into from
Mar 20, 2024
Merged

Add release notes for v1.5 #3120

merged 5 commits into from
Mar 20, 2024

Conversation

aleks-p
Copy link
Contributor

@aleks-p aleks-p commented Mar 19, 2024

@aleks-p aleks-p requested review from a team as code owners March 19, 2024 20:03
@knylander-grafana knylander-grafana added the type/docs Improvements for doc docs. Used by Docs team for project management label Mar 19, 2024
@knylander-grafana knylander-grafana self-assigned this Mar 19, 2024
Copy link
Contributor

@knylander-grafana knylander-grafana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for updating the release notes! These look good.

@knylander-grafana knylander-grafana added the backport release/v1.5 This label will backport a merged PR to the release/v1.5 branch label Mar 20, 2024
@knylander-grafana knylander-grafana merged commit a868886 into main Mar 20, 2024
17 checks passed
@knylander-grafana knylander-grafana deleted the update-changelog-1.5 branch March 20, 2024 20:08
Copy link
Contributor

This PR must be merged before a backport PR will be created.

github-actions bot pushed a commit that referenced this pull request Mar 20, 2024
* Add release notes for v1.5

* Improve wording

* Remove irrelevant release notes

* Make release notes in line with GH release

(cherry picked from commit a868886)
Copy link
Contributor

The backport to release/v1.5 failed:

Validation Failed: "Could not resolve to a node with the global id of 'T_kwDOAG3Mbc4AczmP'."

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3120-to-release/v1.5 origin/release/v1.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x a868886f2838b3997f71c52abe3f0edb31691f8b

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-3120-to-release/v1.5
# Create the PR body template
PR_BODY=$(gh pr view 3120 --json body --template 'Backport a868886f2838b3997f71c52abe3f0edb31691f8b from #3120{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[release/v1.5] Add release notes for v1.5" --body-file - --label "type/docs" --label "backport" --base release/v1.5 --milestone release/v1.5 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-3120-to-release/v1.5

# Create a pull request where the `base` branch is `release/v1.5` and the `compare`/`head` branch is `backport-3120-to-release/v1.5`.

# Remove the local backport branch
git switch main
git branch -D backport-3120-to-release/v1.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release/v1.5 This label will backport a merged PR to the release/v1.5 branch backport-failed type/docs Improvements for doc docs. Used by Docs team for project management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants