Lotus Node v1.33.1 Release

[github-actions]

😶‍🌫 Meta

• Type: Node
• Level: patch
• Related network upgrade version: n/a

🚢 Estimated shipping date

Candidate	Expected Release Date	Release URL
Stable (non-RC)	TBD

🪢 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

• feat(f3): update go-f3, move EC cache to go-f3 #13144
• pion/interceptor vulnerability in lotus (CVE-2025-49140) #13169
• f3 - create a f3 datastore #12320
• API v2 request to Filecoin.GetChainTipset tipset with safe selector results in negative height. #13167
• Another F3 release (0.8.7) with Treat reception of justifications as if reception of the messages they evidence go-f3#342
• f3: lotus f3 powertable commands depend on chain state #13081
• go-libp2p update: chore: update go-libp2p to v0.42 #13179

rcX

• To Be Added

Stable Release (non-RC)

• To Be Added

✅ Release Checklist

⬅️ Before RC1

Section

• Open PR against RELEASE_ISSUE_TEMPLATE.md with title docs(release): v1.33.1 release template improvements for improving future releases.
  • Link to PR:
  • 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.33.1 branch from the master branch and make any further release-related changes to this branch.
  • Note: For critical security patches, fork a new branch from the last stable release/vX.Y.x to expedite the release process.

🏎️ RCs

rc1

Section

[!IMPORTANT]
These PRs should be done in and target the release/v1.33.1 or release/miner/v1.33.1 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
• Run make gen && make docsgen-cli to generate documentation
• Create a draft PR with title build: release Lotus Node v1.33.1-rc1
  • Link to PR:
  • 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)
  • 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 release:
  • Link to issue 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.

rcX

Section

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

Backport PR for rcX

• All explicitly tracked items from Dependencies for releases have landed
• Backported everything with the "backport" label
• Create a PR with title build: backport changes for Node v1.33.1-rcX
  • Link to PR:
• Merge PR
• Remove the "backport" label from all backported PRs (no "backport" issues)

Release PR for rcX

• Update the version string(s) in build/version.go to one ending with '-rcX'.
  • Ensure to update NodeBuildVersion
• Run make gen && make docsgen-cli to generate documentation
• Create a draft PR with title build: release Lotus Node v1.33.1-rcX
  • Link to PR:
  • 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)
  • 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 release:
  • Link to issue comment:

Testing for rcX

[!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.33.1 or release/miner/v1.33.1 branch.

Backport PR for Stable Release (non-RC)

• All explicitly tracked items from Dependencies for releases have landed
• Backported everything with the "backport" label
• Create a PR with title build: backport changes for Node v1.33.1
  • Link to PR:
• Merge PR
• Remove the "backport" label from all backported PRs (no "backport" issues)

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
• Run make gen && make docsgen-cli to generate documentation
• Create a draft PR with title build: release Lotus Node v1.33.1
  • Link to PR:
  • 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)
  • 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 release:
  • Link to issue 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.33.1 branch. Title it chore(release): cherry-pick v1.33.1 changelog back to master
  • Link to PR:
  • 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.
• Review and approve the auto-generated PR in lotus-docs that updates the latest Lotus version information.
• Review and approve the auto-generated PR in homebrew-lotus that updates the homebrew to the latest Lotus version.
• Stage any security advisories for future publishing per policy.

❤️ Contributors

See the final release notes!

⁉️ Do you have questions?

Leave a comment in this ticket!