Skip to content
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

chore(deps): bump github.com/filecoin-project/lotus from 1.32.0-rc3 to 1.32.1 #2003

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 28, 2025

Bumps github.com/filecoin-project/lotus from 1.32.0-rc3 to 1.32.1.

Release notes

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

miner/v1.32.1

The Lotus v1.32.1 release is a MANDATORY patch release, which will deliver the Filecoin network version 25, codenamed “Teep” 🦵. This release sets the upgrade epoch for the Mainnet to Epoch 4867320 - 2025-04-10T23:00:00Z, and correctly sets the F3 activationcontract address to 0xA19080A1Bcb82Bb61bcb9691EC94653Eb5315716. You can find more details about how the F3 activation on Mainnet will be executed in the F3 Activation Procedure.

☢️ Upgrade Warnings ☢️

  • The Lotus v1.32.0 release had an issue where the F3 activation contract address was not set correctly. This release corrects that issue.
  • If you are running the v1.30.0 version of Lotus, please go through the Upgrade Warnings section for the v1.31.0 releases and v1.31.1 before upgrading to this release.
  • The minimum supported Golang version is now 1.23.6 (filecoin-project/lotus#12910).
  • The SupportedProofTypes field has been removed from the Filecoin.StateGetNetworkParams method because it was frequently overlooked during proof type updates and did not accurately reflect the FVM's supported proofs (filecoin-project/lotus#12881).
  • Introduced Agent field to the Filecoin.Version response. Note that this change may be breaking, depending on the clients deserialization capabilities. (filecoin-project/lotus#12904).
  • The --only-cc option has been removed from the lotus-miner sectors extend command.

🏛️ Filecoin network version 25 FIPs

📦 v16 Builtin Actor Bundle

This release candidate uses the v16.0.0

🚚 Migration

All node operators, including storage providers, should be aware that ONE pre-migration is being scheduled 120 epochs before the network upgrade. The migration for the NV25 upgrade is expected to be medium with a bit longer pre-migration compared to the two previous network upgrade.

Pre-Migration is expected to take between 4 to 8 minutes on a SplitStore node. The migration on the upgrade epoch is expected to take 30 seconds on a node with a NVMe-drive and a newer CPU. For nodes running on slower disks/CPU, it is still expected to take around 1 minute. We recommend node operators (who haven't enabled splitstore discard mode) that do not care about historical chain states, to prune the chain blockstore by syncing from a snapshot 1-2 days before the upgrade.

For certain node operators, such as full archival nodes or systems that need to keep large amounts of state (RPC providers), we recommend skipping the pre-migration and run the non-cached migration (i.e., just running the migration at the network upgrade epoch), and schedule for some additional downtime. Operators of such nodes can read the How to disable premigration in network upgrade tutorial.

New Features highlight

... (truncated)

Changelog

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

Node and Miner v1.32.1 / 2025-03-28

The Lotus v1.32.1 release is a MANDATORY patch release, which will deliver the Filecoin network version 25, codenamed “Teep” 🦵. This release sets the upgrade epoch for the Mainnet to Epoch 4867320 - 2025-04-10T23:00:00Z, and correctly sets the F3 activationcontract address to 0xA19080A1Bcb82Bb61bcb9691EC94653Eb5315716. You can find more details about how the F3 activation on Mainnet will be executed in the F3 Activation Procedure.

☢️ Upgrade Warnings ☢️

  • The Lotus v1.32.0 release had an issue where the F3 activation contract address was not set correctly. This release corrects that issue.
  • If you are running the v1.30.0 version of Lotus, please go through the Upgrade Warnings section for the v1.31.0 releases and v1.31.1 before upgrading to this release.
  • The minimum supported Golang version is now 1.23.6 (filecoin-project/lotus#12910).
  • The SupportedProofTypes field has been removed from the Filecoin.StateGetNetworkParams method because it was frequently overlooked during proof type updates and did not accurately reflect the FVM's supported proofs (filecoin-project/lotus#12881).
  • Introduced Agent field to the Filecoin.Version response. Note that this change may be breaking, depending on the clients deserialization capabilities. (filecoin-project/lotus#12904).
  • The --only-cc option has been removed from the lotus-miner sectors extend command.

🏛️ Filecoin network version 25 FIPs

📦 v16 Builtin Actor Bundle

This release candidate uses the v16.0.0

🚚 Migration

All node operators, including storage providers, should be aware that ONE pre-migration is being scheduled 120 epochs before the network upgrade. The migration for the NV25 upgrade is expected to be medium with a bit longer pre-migration compared to the two previous network upgrade.

Pre-Migration is expected to take between 4 to 8 minutes on a SplitStore node. The migration on the upgrade epoch is expected to take 30 seconds on a node with a NVMe-drive and a newer CPU. For nodes running on slower disks/CPU, it is still expected to take around 1 minute. We recommend node operators (who haven't enabled splitstore discard mode) that do not care about historical chain states, to prune the chain blockstore by syncing from a snapshot 1-2 days before the upgrade.

For certain node operators, such as full archival nodes or systems that need to keep large amounts of state (RPC providers), we recommend skipping the pre-migration and run the non-cached migration (i.e., just running the migration at the network upgrade epoch), and schedule for some additional downtime. Operators of such nodes can read the How to disable premigration in network upgrade tutorial.

New Features highlight

... (truncated)

Commits
  • 42d68a5 build: release Lotus Node and Miner v1.32.1 (#12997)
  • 4b612ec feat: set F3 activation contract address as specified in the FRC (#12994) (#1...
  • 0b75709 build: release Lotus Node and Miner v1.32.0 (#12992)
  • 3ac1c40 chore(eth): make EthGetBlockByNumber & EthGetBlockByHash share cache code (#1...
  • 20790e4 chore: set Mainnet nv25 upgrade epoch and update deps (#12986)
  • 2ad22ee feat(shed): lotus-shed miner-fees - to inspect FIP-0100 fees for a miner (#12...
  • 7bf0a98 feat: expose market ProviderSectors access on state-types abstraction (#12978)
  • cdb05a8 fix(test): deflake daily_fees_test
  • a644d54 chore(deps): bump go-state-types to v0.16.0-rc8
  • cc2349a feat: integrate & test FIP-0098 additions (#12968)
  • See full diff in compare view

Dependabot compatibility score

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)

Bumps [github.com/filecoin-project/lotus](https://github.com/filecoin-project/lotus) from 1.32.0-rc3 to 1.32.1.
- [Release notes](https://github.com/filecoin-project/lotus/releases)
- [Changelog](https://github.com/filecoin-project/lotus/blob/v1.32.1/CHANGELOG.md)
- [Commits](filecoin-project/lotus@v1.32.0-rc3...v1.32.1)

---
updated-dependencies:
- dependency-name: github.com/filecoin-project/lotus
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Mar 28, 2025
@LexLuthr LexLuthr closed this Mar 31, 2025
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 31, 2025

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.

@LexLuthr LexLuthr deleted the dependabot/go_modules/github.com/filecoin-project/lotus-1.32.1 branch March 31, 2025 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant