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.30.0-rc1 to 1.30.0-rc2 #172

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 14, 2024

Bumps github.com/filecoin-project/lotus from 1.30.0-rc1 to 1.30.0-rc2.

Release notes

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

miner/v1.30.0-rc2

This is the second release candidate of the upcoming MANDATORY Lotus v1.30.0 release, which will deliver the Filecoin network version 24, codenamed Tuk Tuk 🛺. This release candidate sets the calibration network upgrade to epoch 207879, which corresponds to 2024-10-23T13:30:00Z. F3 is set to be automatically activated one day later at epoch 2081674, which corresponds to 2024-10-24T13:30:00Z.

[!NOTE]

  1. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected October 30th).

☢️ Upgrade Warnings ☢️

  • If you are running the v1.28.x version of Lotus, please go through the Upgrade Warnings section for the v1.28.* releases and v1.29.*, before upgrading to this RC.
  • This release requires a minimum Go version of v1.22.7 or higher.
  • The releases branch has been deprecated with the 202408 split of 'Lotus Node' and 'Lotus Miner'. See https://github.com/filecoin-project/lotus/blob/master/LOTUS_RELEASE_FLOW.md#why-is-the-releases-branch-deprecated-and-what-are-alternatives for more info and alternatives for getting the latest release for both the 'Lotus Node' and 'Lotus Miner' based on the Branch and Tag Strategy.
    • To get the latest Lotus Node tag: git tag -l 'v*' | sort -V -r | head -n 1
    • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

📦 v15 Builtin Actor Bundle

This release candidate uses the v15.0.0-rc1

🚚 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 NV24 upgrade is expected to be light with no heavy pre-migrations:

  • Pre-Migration is expected to take less then 1 minute.
  • The migration on the upgrade epoch is expected to take less than 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 less then 1 minute.
  • RAM usages is expected to be under 20GiB RAM for both the pre-migration and migration.

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.

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed

... (truncated)

Changelog

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

Node and Miner v1.30.0-rc2 / 2024-10-14

This is the second release candidate of the upcoming MANDATORY Lotus v1.30.0 release, which will deliver the Filecoin network version 24, codenamed Tuk Tuk 🛺. This release candidate sets the calibration network upgrade to epoch 207879, which corresponds to 2024-10-23T13:30:00Z. F3 is set to be automatically activated one day later at epoch 2081674, which corresponds to 2024-10-24T13:30:00Z.

[!NOTE]

  1. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected October 30th).

☢️ Upgrade Warnings ☢️

  • If you are running the v1.28.x version of Lotus, please go through the Upgrade Warnings section for the v1.28.* releases and v1.29.*, before upgrading to this RC.
  • This release requires a minimum Go version of v1.22.7 or higher.
  • The releases branch has been deprecated with the 202408 split of 'Lotus Node' and 'Lotus Miner'. See https://github.com/filecoin-project/lotus/blob/master/LOTUS_RELEASE_FLOW.md#why-is-the-releases-branch-deprecated-and-what-are-alternatives for more info and alternatives for getting the latest release for both the 'Lotus Node' and 'Lotus Miner' based on the Branch and Tag Strategy.
    • To get the latest Lotus Node tag: git tag -l 'v*' | sort -V -r | head -n 1
    • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

📦 v15 Builtin Actor Bundle

This release candidate uses the v15.0.0-rc1

🚚 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 NV24 upgrade is expected to be light with no heavy pre-migrations:

  • Pre-Migration is expected to take less then 1 minute.
  • The migration on the upgrade epoch is expected to take less than 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 less then 1 minute.
  • RAM usages is expected to be under 20GiB RAM for both the pre-migration and migration.

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.

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

| Contributor | Commits | Lines ± | Files Changed |

... (truncated)

Commits
  • f8a5c82 build: release Lotus node and miner v1.30.0-rc2 (#12599)
  • 64fcbb7 fix(miner): fix new bug in StateMinerPreCommitDepositForPower calculation (#1...
  • 6f47bca fix(f3): don't return an error on stop if our context was canceled (#12592)
  • 12a5aa1 feat(f3): refactor the F3 participation module to improve testing (#12589)
  • 7c11a8d feat(f3): remove lease-check interval constants
  • ff3afcf fix(f3): handle a case where we might receive no manifest (#12579)
  • 8072385 fix bug in exclude reverted logic (#12588)
  • 272f092 fix(events): handle subscribe and get/fill cases separately
  • 81f4f69 fix(events): address API reverted semantics
  • 8d96568 Fix address network override via env var (#12590)
  • Additional commits viewable 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)

🔗 zboto Link

Bumps [github.com/filecoin-project/lotus](https://github.com/filecoin-project/lotus) from 1.30.0-rc1 to 1.30.0-rc2.
- [Release notes](https://github.com/filecoin-project/lotus/releases)
- [Changelog](https://github.com/filecoin-project/lotus/blob/v1.30.0-rc2/CHANGELOG.md)
- [Commits](filecoin-project/lotus@v1.30.0-rc1...v1.30.0-rc2)

---
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 Oct 14, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 15, 2024

Looks like github.com/filecoin-project/lotus is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Oct 15, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/master/github.com/filecoin-project/lotus-1.30.0-rc2 branch October 15, 2024 07:51
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
None yet
Development

Successfully merging this pull request may close these issues.

0 participants