Lotus Node and Miner v1.34.1 Release

[github-actions]

😶‍🌫 Meta

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

🚢 Estimated shipping date

Candidate	Expected Release Date	Release URL
RC1	TBD
Stable (non-RC)	2025-09-16

🪢 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.

Stable Release (non-RC)

• Update filecoin-ffi submodule from v1.34.0-dev to stable v1.34.0
• Bump version to v1.34.1 in build/version.go
• Update CHANGELOG.md with v1.34.1 patch release notes
• Regenerate documentation via make gen and make docsgen-cli

✅ Release Checklist

Stable Release (non-RC)

Section

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

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.34.1
  • Link to PR: build: release Lotus Node and Miner v1.34.1 #13345
  • 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 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.34.1 branch. Title it chore(release): cherry-pick v1.34.1 changelog back to master
  • Link to PR: chore(release): cherry-pick v1.34.1 changelog back to master #13371
  • 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!

[BigLep]

@TippyFlitsUK : just debugging about the branch confusion. I missed this too. I think maybe there is some confusion about the "Before RC" steps. It seems like that should be labeled something like "Before RC1 (or final release if no RC)". If we had that and kept those steps around I think we would have been guided to create the branch. Do you agree? I've added this to #13270 as something else to fix/improve.

[TippyFlitsUK]

That's a very good point, Steve 👍