Skip to content

Conversation

AgraVator
Copy link
Contributor

No description provided.

@AgraVator AgraVator requested a review from ejona86 October 6, 2025 08:02
Copy link
Member

Choose a reason for hiding this comment

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

There aren't any updates to reference 1.76.0 in this commit. See 28f1425 for an example. Because this is messed up, the tag will also be messed up; so you'll want to git tag -d v1.76.0 and re-create the tag. Since Kannan is OOO to walk you through it, the easiest thing is probably delete the local branch and start over (git checkout master; git branch -D release-v1.76.0) on step 3. In step 5 when you push the branch you'll need to use --force because the branch already exists (git push --force -u origin release-v$MAJOR.$MINOR.$PATCH). Pushing at that point will update this PR; you don't need to close this PR or create a new PR.

Copy link
Contributor Author

@AgraVator AgraVator Oct 6, 2025

Choose a reason for hiding this comment

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

Deleting the branch in my fork, will redo from scratch...

@AgraVator AgraVator closed this Oct 6, 2025
@AgraVator AgraVator deleted the release-v1.76.0 branch October 6, 2025 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants