Lotus Node and Miner v1.32.0/v1.32.1/v1.32.2 Release

[BigLep]

😶‍🌫 Meta

• Type: Node and Miner
• Level: minor
• Related network upgrade version: nv25
  • Scope, dates, and epochs: nv25 Network Upgrade Planning core-devs#183
  • Lotus changelog with Lotus specifics:

🚢 Estimated shipping date

Candidate	Expected Release Date	Release URL
RC1	Week of 2024-12-05	https://github.com/filecoin-project/lotus/releases/tag/v1.32.0-rc1 https://github.com/filecoin-project/lotus/releases/tag/miner%2Fv1.32.0-rc1
RC2	Week of 2024-12-09	https://github.com/filecoin-project/lotus/releases/tag/v1.32.0-rc2 https://github.com/filecoin-project/lotus/releases/tag/miner%2Fv1.32.0-rc2
RC3	2025-03-19	https://github.com/filecoin-project/lotus/releases/tag/v1.32.0-rc3 https://github.com/filecoin-project/lotus/releases/tag/miner%2Fv1.32.0-rc3
Stable (non-RC)	2025-03-27	https://github.com/filecoin-project/lotus/releases/tag/v1.32.0 https://github.com/filecoin-project/lotus/releases/tag/miner%2Fv1.32.0
Stable (non-RC)	2025-03-27	https://github.com/filecoin-project/lotus/releases/tag/v1.32.1 https://github.com/filecoin-project/lotus/releases/tag/miner%2Fv1.32.1
Stable (non-RC)	2025-04-04	https://github.com/filecoin-project/lotus/releases/tag/v1.32.2 https://github.com/filecoin-project/lotus/releases/tag/miner%2Fv1.32.2

🪢 Dependencies for releases

Note

1. This is the set of changes that need to make it in for a given RC. This is effectively the set of changes to cherry-pick from master.
2. They can be checked as done once they land in master.
3. They are presented here for quick reference, but backporting is tracked in each Release Checklist.

rc1

• chore(deps): update actors bundle to v16.0.0-dev #12751
• F3 milestone 2.5 items with a go-f3 release bubbled into Lotus: Release v0.7.3 for Lotus v1.32.0-rc1 go-f3#773
•  chore: bump deps, set calibnet nv25 epoch, change nv25-codename #12754

rc2

•  chore: update log progress on network migrations  #12732
• fix: f3 gen power command being non-deterministic #12764
•  chore: remove IPNI advertisement relay over pubsub via Lotus node #12768
•  feat: optimize ForEachClaim to return only eligible claims #12770
• chore: update to golang crypto 0.31.0 #12775
•  feat(gateway): add F3GetCertificate & F3GetLatestCertificate to gateway #12778
•  chore: unset nv25 upgrade height on Calibnet #12779

rc3 (Calibnet Release)

• chore: upgrade to go-f3 v0.8.3 #12941
•  Benchmark nv25 migration #12959
• feat: nv25 and nv26 - fip-0100 (and some FIP-0098) #12932
• feat(miner): remove batch balancer-related functionality #12919
• chore: update Calibration Teep height #12964

Stable Release (non-RC)

• feat: integrate & test FIP-0098 additions #12968
• chore(deps): bump go-state-types to v0.16.0-rc8 #12973
• feat: expose market ProviderSectors access on state-types abstraction #12978
•  chore(eth): make EthGetBlockByNumber & EthGetBlockByHash share cache code #12979
• feat(shed): lotus-shed miner-fees - to inspect FIP-0100 fees for a miner #12980
•  chore: set Mainnet nv25 upgrade epoch and update deps #12986

Stable Release (v1.32.3)

• v16.0.1 actors bundle
• Calibration TockFixHeight
•  Mainnet new date

✅ Release Checklist

⬅️ Before RC1

Section

• Make sure all Lotus dependencies are updated to the correct versions for the network upgrade
  • Link to Lotus PR: feat: nv25 network skeleton #12707 and chore(deps): update actors bundle to v16.0.0-dev #12751 and chore: bump deps, set calibnet nv25 epoch, change nv25-codename #12754
• Open PR against RELEASE_ISSUE_TEMPLATE.md with title docs(release): v1.32.0 release template improvements for improving future releases.
  • Link to PR: docs(release): v1.32.0 release template improvements #12874
  • There likely aren't any changes at this point, but this can be opened with a small whitespace change so the PR is open and we can more easily hold the standard of making improvements incrementally since improvements are usually better done by collecting changes/notes along the way rather than just thinking about it at the end.
  • This will get merged in a Post Release step.
• Fork a new release/v1.32.0 branch from master and make any further release-related changes to this branch.
• Fork a new release/miner/v1.32.0 branch from master and make any further release-related changes to this branch.
• master branch Version string updates
  • bump the version(s) in build/version.go to v1.32.1-dev.
    • Ensure to update NodeBuildVersion
    • Ensure to update MinerBuildVersion
  • Run make gen && make docsgen-cli before committing changes.
  • Update the CHANGELOG
    • Change the UNRELEASED section header to UNRELEASED v1.32.0
    • Set the UNRELEASED v1.32.0 section's content to be "See https://github.com/filecoin-project/lotus/blob/release/v1.32.0/CHANGELOG.md"
    • Add a new UNRELEASED header to top.
  • Create a PR with title build: update Lotus Node and Miner version to v1.32.1-dev in master
    • Link to PR: build: update Lotus Node and Miner version to v1.32.1-dev in master #12756
  • Merge PR

🏎️ RCs

rc1

Section

[!IMPORTANT]
These PRs should be done in and target the release/v1.32.0 or release/miner/v1.32.0 branch.

Backport PR for rc1

• All explicitly tracked items from Dependencies for releases have landed

Release PR for rc1

• Update the version string(s) in build/version.go to one ending with '-rc1'.
  • Ensure to update NodeBuildVersion
  • Ensure to update MinerBuildVersion
• Run make gen && make docsgen-cli to generate documentation
• Create a draft PR with title build: release Lotus Node and Miner v1.32.0-rc1
  • Link to PR: build: release Lotus Node and Miner v1.32.0-rc1 #12760
  • Opening a PR will trigger a CI run that will build assets, create a draft GitHub release, and attach the assets.
• Changelog prep
  • Go to the releases page and copy the auto-generated release notes into the CHANGELOG
  • Perform editorial review (e.g., callout breaking changes, new features, FIPs, actor bundles)
  • (network upgrade) Specify whether the Calibration or Mainnet upgrade epoch has been specified or not yet.
    • Example where these weren't specified yet: PR #12169
  • Ensure no missing content when spot checking git history
    • Example command looking at git commits: git log --oneline --graph vA.B.C.., where A.B.C correspond to the previous release.
    • Example GitHub UI search looking at merged PRs into master: https://github.com/filecoin-project/lotus/pulls?q=is%3Apr+base%3Amaster+merged%3A%3EYYYY-MM-DD
    • Example gh cli command looking at merged PRs into master and sorted by title to group similar areas (where YYYY-MM-DD is the start search date): gh pr list --repo filecoin-project/lotus --search "base:master merged:>YYYY-MM-DD" --json number,mergedAt,author,title | jq -r '.[] | [.number, .mergedAt, .author.login, .title] | @tsv' | sort -k4
  • Update the PR with the commit(s) made to the CHANGELOG
• Mark the PR "ready for review" (non-draft)
• Merge the PR
  • Merging the PR will trigger a CI run that will build assets, attach the assets to the GitHub release, publish the GitHub release, and create the corresponding git tag.
• Update 🚢 Estimated shipping date table
• Comment on this issue announcing the RC
  • Link to issue comment: Lotus Node and Miner v1.32.0/v1.32.1/v1.32.2 Release #12750 (comment)

Testing for rc1

[!NOTE]
Link to any special steps for testing releases beyond ensuring CI is green. Steps can be inlined here or tracked elsewhere.

rc2

Section

[!IMPORTANT]
These PRs should be done in and target the release/v1.32.0 or release/miner/v1.32.0 branch.

Backport PR for rc2

• All explicitly tracked items from Dependencies for releases have landed
• Backported everything with the "backport" label
• Removed the "backport" label from all backported PRs (no "backport" issues)
• Create a PR with title build: backport changes for Node and Miner v1.32.0-rc2
  • Link to PR: build: backport changes for Node and Miner v1.32.0-rc2 #12776
• Merge PR

Release PR for rc2

• Update the version string(s) in build/version.go to one ending with '-rc2'.
  • Ensure to update NodeBuildVersion
  • Ensure to update MinerBuildVersion
• Run make gen && make docsgen-cli to generate documentation
• Create a draft PR with title build: release Lotus Node and Miner v1.32.0-rc2
  • Link to PR: build: release Lotus Node and Miner v1.32.0-rc2 #12780
  • Opening a PR will trigger a CI run that will build assets, create a draft GitHub release, and attach the assets.
• Changelog prep
  • Go to the releases page and copy the auto-generated release notes into the CHANGELOG
  • Perform editorial review (e.g., callout breaking changes, new features, FIPs, actor bundles)
  • (network upgrade) Specify whether the Calibration or Mainnet upgrade epoch has been specified or not yet.
    • Example where these weren't specified yet: PR #12169
  • Ensure no missing content when spot checking git history
    • Example command looking at git commits: git log --oneline --graph vA.B.C.., where A.B.C correspond to the previous release.
    • Example GitHub UI search looking at merged PRs into master: https://github.com/filecoin-project/lotus/pulls?q=is%3Apr+base%3Amaster+merged%3A%3EYYYY-MM-DD
    • Example gh cli command looking at merged PRs into master and sorted by title to group similar areas (where YYYY-MM-DD is the start search date): gh pr list --repo filecoin-project/lotus --search "base:master merged:>YYYY-MM-DD" --json number,mergedAt,author,title | jq -r '.[] | [.number, .mergedAt, .author.login, .title] | @tsv' | sort -k4
  • Update the PR with the commit(s) made to the CHANGELOG
• Mark the PR "ready for review" (non-draft)
• Merge the PR
  • Merging the PR will trigger a CI run that will build assets, attach the assets to the GitHub release, publish the GitHub release, and create the corresponding git tag.
• Update 🚢 Estimated shipping date table
• Comment on this issue announcing the RC
  • Link to issue comment: Lotus Node and Miner v1.32.0/v1.32.1/v1.32.2 Release #12750 (comment)

Testing for rc2

[!NOTE]
Link to any special steps for testing releases beyond ensuring CI is green. Steps can be inlined here or tracked elsewhere.

rc3

Section

[!IMPORTANT]
These PRs should be done in and target the release/v1.32.0 or release/miner/v1.32.0 branch.

Backport PR for rc3

• All explicitly tracked items from Dependencies for releases have landed
• Backported everything with the "backport" label
• Removed the "backport" label from all backported PRs (no "backport" issues)

Release PR for rc3

• Update the version string(s) in build/version.go to one ending with '-rc3'.
  • Ensure to update NodeBuildVersion
  • Ensure to update MinerBuildVersion
• Run make gen && make docsgen-cli to generate documentation
• Create a draft PR with title build: release Lotus Node and Miner v1.32.0-rc3
  • Link to PR: build: release Lotus Node and Miner v1.32.0-rc3 #12965
  • Opening a PR will trigger a CI run that will build assets, create a draft GitHub release, and attach the assets.
• Changelog prep
  • Go to the releases page and copy the auto-generated release notes into the CHANGELOG
  • Perform editorial review (e.g., callout breaking changes, new features, FIPs, actor bundles)
  • (network upgrade) Specify whether the Calibration or Mainnet upgrade epoch has been specified or not yet.
    • Example where these weren't specified yet: PR #12169
  • Ensure no missing content when spot checking git history
    • Example command looking at git commits: git log --oneline --graph vA.B.C.., where A.B.C correspond to the previous release.
    • Example GitHub UI search looking at merged PRs into master: https://github.com/filecoin-project/lotus/pulls?q=is%3Apr+base%3Amaster+merged%3A%3EYYYY-MM-DD
    • Example gh cli command looking at merged PRs into master and sorted by title to group similar areas (where YYYY-MM-DD is the start search date): gh pr list --repo filecoin-project/lotus --search "base:master merged:>YYYY-MM-DD" --json number,mergedAt,author,title | jq -r '.[] | [.number, .mergedAt, .author.login, .title] | @tsv' | sort -k4
  • Update the PR with the commit(s) made to the CHANGELOG
• Mark the PR "ready for review" (non-draft)
• Merge the PR
  • Merging the PR will trigger a CI run that will build assets, attach the assets to the GitHub release, publish the GitHub release, and create the corresponding git tag.
• Update 🚢 Estimated shipping date table
• Comment on this issue announcing the RC
  • Link to issue comment: Lotus Node and Miner v1.32.0/v1.32.1/v1.32.2 Release #12750 (comment)

Testing for rc3

[!NOTE]
Link to any special steps for testing releases beyond ensuring CI is green. Steps can be inlined here or tracked elsewhere.

Stable Release (non-RC)

Section

[!IMPORTANT]
These PRs should be done in and target the release/v1.32.0 or release/miner/v1.32.0 branch.

Backport PR for Stable Release (non-RC)

• All explicitly tracked items from Dependencies for releases have landed
• Backported everything with the "backport" label
• Removed the "backport" label from all backported PRs (no "backport" issues)
• Create a PR with title build: backport changes for Node and Miner v1.32.0
  • Link to PR: chore: backport to release/v1.32.0 branch #12989
• Merge PR

Release PR for Stable Release (non-RC)

• Update the version string(s) in build/version.go to one *NOT ending with 'rcX'.
  • Ensure to update NodeBuildVersion
  • Ensure to update MinerBuildVersion
• Run make gen && make docsgen-cli to generate documentation
• Create a draft PR with title build: release Lotus Node and Miner v1.32.0
  • Link to PR: build: release Lotus Node and Miner v1.32.0 #12992
  • Opening a PR will trigger a CI run that will build assets, create a draft GitHub release, and attach the assets.
• Changelog prep
  • Go to the releases page and copy the auto-generated release notes into the CHANGELOG
  • Perform editorial review (e.g., callout breaking changes, new features, FIPs, actor bundles)
  • (network upgrade) Ensure the Mainnet upgrade epoch is specified.
  • Ensure no missing content when spot checking git history
    • Example command looking at git commits: git log --oneline --graph vA.B.C.., where A.B.C correspond to the previous release.
    • Example GitHub UI search looking at merged PRs into master: https://github.com/filecoin-project/lotus/pulls?q=is%3Apr+base%3Amaster+merged%3A%3EYYYY-MM-DD
    • Example gh cli command looking at merged PRs into master and sorted by title to group similar areas (where YYYY-MM-DD is the start search date): gh pr list --repo filecoin-project/lotus --search "base:master merged:>YYYY-MM-DD" --json number,mergedAt,author,title | jq -r '.[] | [.number, .mergedAt, .author.login, .title] | @tsv' | sort -k4
  • Update the PR with the commit(s) made to the CHANGELOG
• Mark the PR "ready for review" (non-draft)
• Merge the PR
  • Merging the PR will trigger a CI run that will build assets, attach the assets to the GitHub release, publish the GitHub release, and create the corresponding git tag.
• Update 🚢 Estimated shipping date table
• Comment on this issue announcing the RC
  • Link to issue comment: Lotus Node and Miner v1.32.0/v1.32.1/v1.32.2 Release #12750 (comment)

Testing for Stable Release (non-RC)

[!NOTE]
Link to any special steps for testing releases beyond ensuring CI is green. Steps can be inlined here or tracked elsewhere.

➡ Post-Release

Section

• Open a PR against master cherry-picking the CHANGELOG commits from the release/v1.32.0 branch. Title it chore(release): cherry-pick v1.32.0 changelog back to master
  • Link to PR: chore(release): cherry-pick v1.32.0&v1.32.1 changelog back to master #13001
  • Assuming we followed the process of merging changes into master first before backporting to the release branch, the only changes should be CHANGELOG updates.
• Finish updating/merging the RELEASE_ISSUE_TEMPLATE.md PR from Before RC1 with any improvements determined from this latest release iteration.

❤️ Contributors

See the final release notes!

⁉️ Do you have questions?

Leave a comment in this ticket!

[BigLep]

Created using #12749 with ./release create-issue --create-on-github --type both --tag 1.32.0 --level minor --network-upgrade 25 --rc1-date "Week of 2024-12-02" --stable-date "Week of 2024-12-16"

[sin3point14]

The upgrade announcement says:

The Filecoin CalibrationNet will undergo an upgrade to network version 25, codenamed "Teep 🦵", at epoch 2235454, on 2024-12-16T23:00:00Z.

This issue says:

Stable (non-RC) Week of 2024-12-16 (estimate)

https://github.com/filecoin-project/lotus/releases/tag/miner/v1.32.0-rc1 says:

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

I think the 18 Dec in the release notes is a typo, since it lies after 16th. But even in this issue, the stable release is expected to be on 16 dec which is the same day as the upgrade... which imo gives very little time for node operators to perform the upgrade, unless I am misunderstanding something