tersec
tersec
Legacy sync has been removed: https://github.com/status-im/nimbus-eth1/pull/2237
Does using a commit hash not work for this purpose?
`jenkins/nimbus-eth2/linux/x86_64/nimv2` CI failure is because https://github.com/nim-lang/Nim/issues/23568
(mistaken close) - https://github.com/status-im/nimbus-eth2/pull/6141 - https://github.com/status-im/nimbus-eth2/pull/6142 - https://github.com/status-im/nimbus-eth2/pull/6143
- https://github.com/status-im/nimbus-eth2/pull/6147
Does https://github.com/vacp2p/nim-libp2p/pull/1099 do some of what this does?
https://github.com/status-im/nimbus-eth2/pull/6412
Yeah, it's always a gamble with retargeting, because it's either: a) ask them to do it on their own, which is the human version of "obnoxious" here; b) just try...
- https://github.com/status-im/nimbus-eth2/pull/6103
One edge case here is Dependabot, which uses `stable` and might not be able to use any other branch except if it were the default (i.e. navigating to `https://github.com/status-im/nimbus-eth2/` navigated...