docs: Add release notes for v1.8 #3557
Merged
Conversation
This file contains 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
korniltsev
added
backport release/v1.8
|
Hello @korniltsev!
Please, if the current pull request addresses a bug fix, label it with the |
marcsanmi
reviewed
Sep 13, 2024
Co-authored-by: Marc Sanmiquel <[email protected]>
github-actions bot
pushed a commit
that referenced
this pull request
Sep 13, 2024
* docs: Add release notes for v1.8 * Update docs/sources/release-notes/v1-8.md Co-authored-by: Marc Sanmiquel <[email protected]> --------- Co-authored-by: Marc Sanmiquel <[email protected]> (cherry picked from commit 25b12bf)
|
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-3557-to-release/v1.8 origin/release/v1.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 25b12bf34acf45f26ba93a46745a39446f95da1aWhen the conflicts are resolved, stage and commit the changes: If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-3557-to-release/v1.8
# Create the PR on GitHub
gh pr create --title '[release/v1.8] docs: Add release notes for v1.8' --body 'Backport 25b12bf34acf45f26ba93a46745a39446f95da1a from #3557' --label 'documentation' --label 'type/docs' --label 'backport' --base release/v1.8 --milestone release/v1.8 --webOr, 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-3557-to-release/v1.8
# Create a pull request where the `base` branch is `release/v1.8` and the `compare`/`head` branch is `backport-3557-to-release/v1.8`.
# Remove the local backport branch
git switch main
git branch -D backport-3557-to-release/v1.8 |
korniltsev
added a commit
that referenced
this pull request
Sep 13, 2024
* docs: Add release notes for v1.8 * Update docs/sources/release-notes/v1-8.md Co-authored-by: Marc Sanmiquel <[email protected]> --------- Co-authored-by: Marc Sanmiquel <[email protected]> (cherry picked from commit 25b12bf) Co-authored-by: Tolya Korniltsev <[email protected]>
This was referenced Sep 20, 2024
jdbaldry
added a commit
to grafana/agent
that referenced
this pull request
Sep 27, 2024
Use the default token injected into workflows since the GH_BOT_ACCESS_TOKEN is revoked. The default token doesn't have the permission used for unassigning default reviewers. If you don't have it, you get cryptic comments posted back on the PR after the backport PRs are opened with the message `Validation Failed: "Could not resolve to a node with the global id of '<NODE ID>."` Like in grafana/pyroscope#3557 (comment) Behavior was documented in grafana/grafana-github-actions#226 and made configurable in grafana/grafana-github-actions#227 `removeDefaultReviewers: false` instructs the workflow to not try to avoid the error but will of course not remove the default reviewers assigned on the backport PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.