Repository navigation
chore(deps): bump IPNetwork2 from 4.3.0 to 5.0.1 - #10453
Open
aleksandr-miheichev wants to merge 1 commit into
Open
aleksandr-miheichev wants to merge 1 commit into
aleksandr-miheichev wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bump IPNetwork2 from 4.3.0 to 5.0.1, including the 5.x thread-safety and collection fixes. The existing
Parse,Subtract,SupernetandTotalusages need no API migration, and the package still provides anet10.0asset.Add 18 integration cases for generated TUN routes and Fake DNS pool sizes, covering IPv4/IPv6 separation, overlapping and duplicate exclusions, host-address boundaries, full-family exclusions, large IPv6 pools and invalid-range fallbacks.
Validation on source
d8ebfa3(A/B CI run):--maximum-parallel-tests 1.InstanceLockOwnerCanBeReadWhileAnotherProcessHoldsTheLocktest fails because reading the held lock's owner returns null. The CI run therefore has two failing baseline/candidate jobs.The isolated CI harness is kept on a separate fork branch and is excluded from this PR.