Lotus Release v1.29.1

[BigLep]

Lotus Node1.29.1 Release

😶‍🌫 Meta

• Scope: Node PATCH
• Is this linked with a network upgrade, and thus mandatory? No
• Related network upgrade version: n/a

🚢 Estimated shipping date

Candidate	Date	Release URL
Stable (non-RC)	2024-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.

• deps: bls: downgrade bls library #12469

✅ Release Checklist

Before RC1

• (patch release) Fork a new branch (release/v1.29.1) from the last stable release/v1.29.0 and make any further release-related changes to this branch.

Stable (non-RC) Release

Important

These PRs should be done in and target the release/v1.29.1 or release/miner/v1.29.1 branch.

Backport PR

• 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|miner v1.29.1-rcX
  • Link to PR: this is happening in the Release PR below
• Merge PR: this is happening in the Release PR below

Release PR

• Update the version string in build/version.go to one NOT ending with '-rcX'

  • Ensure to update the appropriate version string based on whether you are creating a node release (NodeBuildVersion), a miner release (MinerBuildVersion), or both.

• Run make gen && make docsgen-cli to generate documentation

• Changelog prep

  • Go to the releases page and copy the auto generated changelog into your release PR and adjust the changelog accordingly.
  • 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

• Create a PR with title build: release v1.29.1

  • Link to PR: chore: prep v1.29.1 #12471
  • Opening a PR will trigger a CI run that will build assets, create a draft GitHub release, and attach the assets.

• Merge the PR

  • Opening 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.

• Copy/paste changelog content into the release

• Update 🚢 Estimated shipping date table

• Comment on this issue announcing the release

  • Link to issue comment: Lotus Release v1.29.1 #12470 (comment)

Post-Release

• Open a pull request against master cherry-picking the CHANGELOG commits from the release/v1.29.1 branch.
  • 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.

❤️ Contributors

See the final release notes!

⁉️ Do you have questions?

Leave a comment in this ticket!

[BigLep]

PR for this release: #12471

[rjan90]

Lotus v1.29.1 release has now been published: https://github.com/filecoin-project/lotus/releases/tag/v1.29.1

[BigLep]

PR (that needs to be filled in) for updating the release process based on lessons learned: #12473

[BigLep]

Closing since the release was released and the release template updates were meged: #12473