Lotus Node v1.29.0 Release

[BigLep]

Lotus Node 1.29.0 Release

😶‍🌫 Meta

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

🚢 Estimated shipping date

Candidate	Date	Release URL
RC1	Week of 2024-08-19	https://github.com/filecoin-project/lotus/releases/tag/v1.29.0-rc1
Stable (non-RC)	Week of 2024-09-01	https://github.com/filecoin-project/lotus/releases/tag/v1.29.0

🪢 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!: gateway: fix rate limiting, better stateful handling #12327

Stable (non-RC)

• StateGetBeaconEntry uses drand client to look up round instead of using tipset data #12414
  • Noted in the changelog that we are releasing v1.29.0 without this fix.

✅ Release Checklist

Before RC1

• Open PR against RELEASE_ISSUE_TEMPLATE.md with title docs(v1.29.0): release template improvements for improving future releases.
  • Link to PR: docs(release): v1.28.2 and v1.29.0 release template improvements #12378
  • This will get merged in a Post Release step, but improvements are better done by collecting notes along the way rather than just thinking about it at the end.
• Fork a new branch (release/v1.29.0 or release/miner/v1.29.0) 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.29.1-dev.
    • 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 before committing changes.
  • Create a PR with title build: v1.29.1 set initial version string
    • Link to PR: build: update Lotus Node version to v1.29.1-dev in master #12409
  • Merge PR

RCs

RC1

Important

These PRs should be done in and target the release/v1.29.0 or release/miner/v1.29.0 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 v1.29.0-rcX
  • Link to PR:
• Merge PR

Release PR

• Update the version string(s) in build/version.go to one 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
  • 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: `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.0-rcX
  • Link to PR: build: release Lotus node v1.29.0-rc1 #12410
  • 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.
• Update 🚢 Estimated shipping date table
• Comment on this issue announcing the RC
  • Link to issue comment: Lotus Node v1.29.0 Release #12343 (comment)

Testing

Note

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

Stable (non-RC) Release

Important

These PRs should be done in and target the release/v1.29.0 or release/miner/v1.29.0 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)

Release PR

• Update the version string(s) 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
  • 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: `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.0
  • Link to PR: build: release Lotus node v1.29.0 #12422
  • 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.
• Update 🚢 Estimated shipping date table
• Comment on this issue announcing the RC
  • Link to issue comment: Lotus Node v1.29.0 Release #12343 (comment)

Post-Release

• Open a pull request against master with a merge of the release/v1.29.0 branch.
  • Conflict resolution should ignore the changes to version.go (keep the -dev version from master).
  • Link to PR: chore(release): cherry-pick v1.29.0 changelog back to master #12425
• 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]

@rjan90 : FYI that the issue description has been populated with the latest https://github.com/filecoin-project/lotus/blob/master/documentation/misc/RELEASE_ISSUE_TEMPLATE.md

I did the initial setup steps listed in the hidden comments. In the process I found a few things to edit in the template and so created the PR for that here: #12373

[BigLep]

Replacement PR where tracking release improvements: #12378

[rjan90]

2024-08-15

Updated estimated shipping dates, due to the need for landing patch releases for Lotus Node | Lotus Miner. Estimate that RC1 will be out early next week.

Candidate	Date	Release URL
RC1	Week of 2024-08-19

[rjan90]

2024-08-23

The first release candidate of Lotus Node v1.29.0 has been shipped: https://github.com/filecoin-project/lotus/releases/tag/v1.29.0-rc1

[rjan90]

2024-09-01

The stable release of Lotus Node v1.29.0 has been shipped: https://github.com/filecoin-project/lotus/releases/tag/v1.29.0