-
Notifications
You must be signed in to change notification settings - Fork 3
chore: bump golang.org/x/crypto from 0.36.0 to 0.45.0 #480
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
Open
dependabot
wants to merge
13
commits into
master
Choose a base branch
from
dependabot/go_modules/golang.org/x/crypto-0.45.0
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
chore: bump golang.org/x/crypto from 0.36.0 to 0.45.0 #480
dependabot
wants to merge
13
commits into
master
from
dependabot/go_modules/golang.org/x/crypto-0.45.0
Conversation
This file contains hidden or 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
9c427c4 to
aa976e5
Compare
## Description Skipping `should process blocks` test due to holesky deprecation and hoodi/sepolia doesn't have `RewardsClaimed` event yet. ## Type of change - [x] Chore (non-breaking change which does not add functionality) ## How Has This Been Tested? Passing CI test. ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [x] Any dependent changes have been merged and published in downstream modules - [x] I have checked my code and corrected any misspellings
aa976e5 to
b502158
Compare
## Description ### Testnet Hoodi Upgrades existing contracts (adds new implementation addresses): ``` DelegationManager: 0x6fe5ebe3ed0f4b2419263868efb5cc640e541407 StrategyManager: 0xfc868562d93c4dc192419e970c220279cdab7b26 AVSDirectory: 0xe368218addc4d2ddc5b0afd70f5878dd8c1713eb AllocationManager: 0x4a3027fc3ae9593874123df96e21e89a698cd7d9 RewardsCoordinator: 0x4a93d276ea78b48be9d8bb864bacdd5d5a713084 EigenPodManager: 0x0f264e714a3c03309f4041db26229ef4e9b00f5c ``` Adds new contracts (both proxy and implementation): ``` ReleaseManager: proxy 0xe863060013cb95473b96f7c3e1444e3e3df65671, impl 0x7a2b8c559a8c8c71a9d364ad250fce5a24b18f5d CrossChainRegistry: proxy 0x9269432451965996be7796582c062cb0795d3e8b, impl 0x1bf65df60184a4a112742ce07f857739fedefbc0 OperatorTableUpdater: proxy 0xb02a15c6bd0882b35e9936a9579f35fb26e11476, impl 0x5dd026aa1c431858e439736d063111763243acae ECDSACertificateVerifier: proxy 0xb3cd1a457dea9a9a6f6406c6419b1c326670a96f, impl 0xe867777f7c45cf6af9b08c7ad62b37c1be61dd25 BN254CertificateVerifier: proxy 0xff58a373c18268f483c1f5ca03cf885c0c43373a, impl 0xe5d02648ddd59ba688846fb5d01f738da6c1ffcb TaskMailbox: proxy 0xb99cc53e8db7018f557606c2a5b066527bf96b26, impl 0xda35d6af400ef38e91bf3eb6c57d9e8d1bf35e36 ``` ### Testnet Sepolia Same contracts upgraded + adding missing KeyRegistrar contract ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [x] Any dependent changes have been merged and published in downstream modules - [x] I have checked my code and corrected any misspellings
fix test fix time to utc fix time time utc fix fix
#474) ## Description ### 1. Database Migration (`202511141700_withdrawalQueueAndAllocationRounding`) - Enhanced `queued_slashing_withdrawals` table with timing columns for 14-day withdrawal tracking: - `completed`, `completion_*` - Completion tracking - Enhanced `operator_allocations` table with rounding support: - `effective_date` - Rounded date when allocation/deallocation takes effect ### 2. Allocation/Deallocation Rounding Logic (Sabine Fork) Implements day-boundary rounding to prevent gaming and mimic existing registration behavior: - **Allocations (increases)**: Round **UP** to next day → starts earning tomorrow - **Deallocations (decreases)**: Round **DOWN** to current day → stops earning immediately - **No change**: Round **DOWN** to current day (conservative default) ### 3. Dual Behavior Implementation Maintains backward compatibility with fork-based behavior switching: - **Before Sabine fork**: Uses old behavior (no rounding, date fields are NULL) - **After Sabine fork**: Applies rounding logic and populates date fields - Model continues processing allocations from Brazos fork onwards ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? Unit tests ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [x] Any dependent changes have been merged and published in downstream modules - [x] I have checked my code and corrected any misspellings
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.36.0 to 0.45.0. - [Commits](golang/crypto@v0.36.0...v0.45.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.45.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
b502158 to
a6f4161
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Bumps golang.org/x/crypto from 0.36.0 to 0.45.0.
Commits
4e0068cgo.mod: update golang.org/x dependenciese79546essh: curb GSSAPI DoS risk by limiting number of specified OIDsf91f7a7ssh/agent: prevent panic on malformed constraint2df4153acme/autocert: let automatic renewal work with short lifetime certsbcf6a84acme: pass context to requestb4f2b62ssh: fix error message on unsupported cipher79ec3a5ssh: allow to bind to a hostname in remote forwarding122a78fgo.mod: update golang.org/x dependenciesc0531f9all: eliminate vet diagnostics0997000all: fix some commentsYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.