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

Update release workflow to be v2 compatible #3375

Merged

Conversation

simonswine
Copy link
Contributor

@simonswine simonswine commented Jun 21, 2024

I am currently trying to cut a v1.6.1 to address #3355 and this was missed as part of #3347

@simonswine simonswine added type/bug Something isn't working backport release/v1.6 This label will backport a merged PR to the release/v1.6 branch labels Jun 21, 2024
@simonswine simonswine marked this pull request as ready for review June 21, 2024 13:17
@simonswine simonswine requested a review from a team as a code owner June 21, 2024 13:17
Copy link
Contributor

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

1 similar comment
Copy link
Contributor

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

@simonswine simonswine merged commit a7a0a82 into grafana:main Jun 21, 2024
18 checks passed
github-actions bot pushed a commit that referenced this pull request Jun 21, 2024
This was missed as part of #3347

(cherry picked from commit a7a0a82)
Copy link
Contributor

The backport to release/v1.6 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-3375-to-release/v1.6 origin/release/v1.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x a7a0a823ea881224692cae3f23c935911d48796e

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-3375-to-release/v1.6
# Create the PR body template
PR_BODY=$(gh pr view 3375 --json body --template 'Backport a7a0a823ea881224692cae3f23c935911d48796e from #3375{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.6] Update release workflow to be v2 compatible' --body-file - --label 'type/bug' --label 'backport' --base release/v1.6 --milestone release/v1.6 --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-3375-to-release/v1.6

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

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

simonswine added a commit that referenced this pull request Jun 21, 2024
This was missed as part of #3347

(cherry picked from commit a7a0a82)

Co-authored-by: Christian Simon <simon@swine.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release/v1.6 This label will backport a merged PR to the release/v1.6 branch backport-failed type/bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants