chore(deps): bump github.com/filecoin-project/lotus from 1.24.0-rc5 to 1.25.0-rc5

[dependabot]

Bumps github.com/filecoin-project/lotus from 1.24.0-rc5 to 1.25.0-rc5.

Release notes

Sourced from github.com/filecoin-project/lotus's releases.

v1.25.0-rc5

This is the fifth release candidate of the upcoming OPTIONAL release Lotus v1.25.0. This optional release also supports the Filecoin network version 21 upgrade, codenamed Watermelon 🍉, in addition to the numerous improvements and enhancements for node operators, ETH RPC-providers and storage providers.

❗ Mainnet Upgrade Date Update

Mainnet upgrade date has been adjusted due to the rescope of nv21 & retesting on test network, as well as giving the community enough time to upgrade their infrastructure.

The new date and epoch for the Mainnet nv21 upgrade has therefore been set to epoch 3469380 - 2023-12-12T13:30:00Z.

FIP0070 descoped for nv21

FIP0070: Allow SPs to move partitions between deadlines was originally scoped for network version 21. However, during the testing on calibrationnet testing, this FIP has proven to be quite error prune to implement due to the complexity of the protocol and a couple bugs were discovered.

As the path to resolving this bug is not yet clear, core devs have decided to descope FIP-0070 from the upcoming nv21 upgrade ensure the security and stability of the network post upgrade.

Calibration WatermelonFix2

For the calibration network, the descoping of FIP0070 means that we will need to do another CodeCID migration to drop FIP0070 from nv21, and to get the test network into a state which will be similar to when the mainnet upgrades to nv21.

This migration will happen at epoch 1108174 - 2023-11-21T13:00:00Z.

Make sure to upgrade you calibration network nodes and storage providers to v1.24.0-rcx & ^ before this epoch.

☢️ Upgrade Warnings ☢️

• Please remove and clone a new Lotus repo (git clone https://github.com/filecoin-project/lotus.git) when upgrading to this version.
• This feature release requires a minimum Go version of v1.20.7 or higher to successfully build Lotus. Go version 1.21.x is not supported yet.
• EthRPC providers, please check out the new tracing API to Lotus RPC

⭐️ Highlights ⭐️

Unsealing bugfixes and enhancements

This feature release introduces significant improvements and bugfixes with regards to unsealing, and ensures that unsealing operates as one would expect. Consequently, unsealing of all sector types (deal sectors, snap-sectors without sector keys, and snap-sectors with sector keys) now all function seamlessly.

Some additional unsealing improvements are:

• Unsealing on workers with only sealing paths works. 🎉
• Transferring unsealed files to long-term storage upon successful unsealing. ➡️
• Ensuring no residual files in sealing paths post a successful unsealing operation. 🧹

SupraSeal C2

Lotus-workers can now be built to leverage the SupraSeal C2 sealing optimizations in your sealing pipeline. The code optimizations are currently behind the FFI_USE_CUDA_SUPRASEAL feature flag. We advice users to test this feature on a test-network, before trying to use it on the mainnet. Users can test out the feature by building their lotus-workers by exporting the FFI_USE_CUDA_SUPRASEAL=1 enviroment variable, and building from source. For questions about the SupraSeal C2 sealing optimizations, reach out in the #fil-proofs or the #dsa-sealing slack channel.

New features

• feat: add Eip155ChainID to StateGetNetworkParams (filecoin-project/lotus#10987)
• feat: profiling: state summary and visualization (filecoin-project/lotus#11012)
• feat: snapshot: remove existing chain (filecoin-project/lotus#11032)

... (truncated)

Changelog

Sourced from github.com/filecoin-project/lotus's changelog.

v 1.25.0-rc5 / 2023-11-16

This is the fifth release candidate of the upcoming OPTIONAL release Lotus v1.25.0. This optional release also supports the Filecoin network version 21 upgrade, codenamed Watermelon 🍉, in addition to the numerous improvements and enhancements for node operators, ETH RPC-providers and storage providers.

❗ Mainnet Upgrade Date Update

Mainnet upgrade date has been adjusted due to the rescope of nv21 & retesting on test network, as well as giving the community enough time to upgrade their infrastructure.

The new date and epoch for the Mainnet nv21 upgrade has therefore been set to epoch 3469380 - 2023-12-12T13:30:00Z.

FIP0070 descoped for nv21

FIP0070: Allow SPs to move partitions between deadlines was originally scoped for network version 21. However, during the testing on calibrationnet testing, this FIP has proven to be quite error prune to implement due to the complexity of the protocol and a couple bugs were discovered.

As the path to resolving this bug is not yet clear, core devs have decided to descope FIP-0070 from the upcoming nv21 upgrade ensure the security and stability of the network post upgrade.

Calibration WatermelonFix2

For the calibration network, the descoping of FIP0070 means that we will need to do another CodeCID migration to drop FIP0070 from nv21, and to get the test network into a state which will be similar to when the mainnet upgrades to nv21.

This migration will happen at epoch 1108174 - 2023-11-21T13:00:00Z.

Make sure to upgrade you calibration network nodes and storage providers to v1.24.0-rcx & ^ before this epoch.

☢️ Upgrade Warnings ☢️

• Please remove and clone a new Lotus repo (git clone https://github.com/filecoin-project/lotus.git) when upgrading to this version.
• This feature release requires a minimum Go version of v1.20.7 or higher to successfully build Lotus. Go version 1.21.x is not supported yet.
• EthRPC providers, please check out the new tracing API to Lotus RPC

⭐️ Highlights ⭐️

Unsealing bugfixes and enhancements

This feature release introduces significant improvements and bugfixes with regards to unsealing, and ensures that unsealing operates as one would expect. Consequently, unsealing of all sector types (deal sectors, snap-sectors without sector keys, and snap-sectors with sector keys) now all function seamlessly.

Some additional unsealing improvements are:

• Unsealing on workers with only sealing paths works. 🎉
• Transferring unsealed files to long-term storage upon successful unsealing. ➡️
• Ensuring no residual files in sealing paths post a successful unsealing operation. 🧹

SupraSeal C2

Lotus-workers can now be built to leverage the SupraSeal C2 sealing optimizations in your sealing pipeline. The code optimizations are currently behind the FFI_USE_CUDA_SUPRASEAL feature flag. We advice users to test this feature on a test-network, before trying to use it on the mainnet. Users can test out the feature by building their lotus-workers by exporting the FFI_USE_CUDA_SUPRASEAL=1 enviroment variable, and building from source. For questions about the SupraSeal C2 sealing optimizations, reach out in the #fil-proofs or the #dsa-sealing slack channel.

New features

• feat: add Eip155ChainID to StateGetNetworkParams (filecoin-project/lotus#10987)
• feat: profiling: state summary and visualization (filecoin-project/lotus#11012)

... (truncated)

Commits

• 44c27f7 Merge pull request #11425 from filecoin-project/phi-v1250rc5
• f467be7 update changelog
• 8f9da34 Merge pull request #11422 from filecoin-project/asr/backport-calib-25
• a71ad24 chore: release: update changelog and version for v1.25.0
• 7b310ba feat: chain: light-weight patch to fix calibrationnet again by removing move_...
• 11b21d5 Merge pull request #11414 from filecoin-project/phi-backport-11408-v1250
• 1234a6e Revert move-partitions cmd
• ce6cbcb Merge pull request #11397 from filecoin-project/phi-backport-11395-v1250
• f02062b Merge pull request #11400 from filecoin-project/phi/v1250rc4
• c95802a Push correct *.json.gz
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

🔗 zboto Link

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.