Skip to content

Conversation

@ceyonur
Copy link

@ceyonur ceyonur commented Apr 10, 2025

Why this should be merged

Release for v1.13.14-0.2.0

How this works

Bumps and cherry picks

How this was tested

CI

Choose a reason for hiding this comment

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

Was this applied correctly? Seems like there are too many returns

@StephenButtolph
Copy link

I don't think this really matters - but based on the release process I feel like the last commit / PR title should be chore: release v1.13.14-0.2.0.release

NathanBSC and others added 4 commits April 10, 2025 22:23
…thereum#29644)

* eth/gasprice: add query limit for FeeHistory to defend DDOS attack

* fix return values after cherry-pick

---------

Co-authored-by: Eric <[email protected]>
* upgrade lock usage

* revert unnecessary change
Fixes an error when the block is not found in debug methods.
@ceyonur ceyonur force-pushed the ceyonur/release/v1.13.14-0.2.0 branch from 9fac9c3 to c89170f Compare April 10, 2025 19:24
@StephenButtolph
Copy link

I don't think this really matters - but based on the release process I feel like the last commit / PR title should be chore: release v1.13.14-0.2.0.release

Turns out it does matter as CI is failing because of it

@ceyonur ceyonur force-pushed the ceyonur/release/v1.13.14-0.2.0 branch from c89170f to 176cf48 Compare April 10, 2025 19:38
@ceyonur ceyonur changed the title chore: release v1.13.14-0.2.0 chore: release v1.13.14-0.2.0.release Apr 10, 2025
@ceyonur ceyonur closed this Apr 10, 2025
@ceyonur ceyonur deleted the ceyonur/release/v1.13.14-0.2.0 branch April 10, 2025 19:51
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.

9 participants