Skip to content

Conversation

@ARR4N
Copy link
Collaborator

@ARR4N ARR4N commented Oct 29, 2024

Caution

Please do not merge via GitHub UI. I will fast-forward merge from the command line.

Why this should be merged

Release candidate for v1.13.14-0.1.0. See this discussion re versioning.

How this works

Branches off latest main and cherry-picks a single commit from geth.

Note

I still need to document how release branches will work but, in summary, they will include upstream cherry-picks that will be rebased to form future releases and dropped when already included in main.

How this was tested

CI

@ARR4N ARR4N requested review from a team, ceyonur, darioush and michaelkaplan13 and removed request for a team October 29, 2024 07:02
@ARR4N ARR4N marked this pull request as ready for review October 29, 2024 07:05
…ereum#29514)

Cherry-pick of `69f815f6f5791e0e48160bdad284773d0ffb1ba9`.
@ARR4N ARR4N force-pushed the arr4n/release/1.13.14-0.1.0-rc.1 branch from 12dc8c8 to 5bb3f0d Compare October 29, 2024 07:31
@ARR4N ARR4N deleted the branch release/1.13.14-0.1.0-rc.1 October 29, 2024 07:33
@ARR4N ARR4N closed this Oct 29, 2024
@ARR4N ARR4N reopened this Oct 29, 2024
@ARR4N
Copy link
Collaborator Author

ARR4N commented Oct 29, 2024

Workflows weren't automatically running so I had to merge #67, force-push my branch, and replace the target release/0.1.13... branch. Teething problems :)

@ARR4N ARR4N merged commit 5bb3f0d into release/1.13.14-0.1.0-rc.1 Oct 29, 2024
5 of 6 checks passed
@ARR4N ARR4N deleted the arr4n/release/1.13.14-0.1.0-rc.1 branch October 29, 2024 21:31
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.

3 participants