Lotus Node v1.36.2 Release

[github-actions]

Meta

• Type: Node
• Level: patch
• Release flow: no-rc (resolved from auto)
• Related network upgrade version: n/a

Estimated shipping date

//: # (If/when we know an exact date, remove the "week of".)
//: # (If a date week is an estimate, annotate with "estimate".)

Candidate	Expected Release Date	Release URL
Stable Release	TBD

Dependencies for releases

Note

1. This is the set of changes that need to make it in for a given release target.
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 the corresponding release checklist.

Stable Release

• Add linked PRs/issues for changes that must land before Stable Release, or write "No additional dependencies for Stable Release" and mark the corresponding dependency checkpoint complete when confirmed.

Release Checklist

Release Setup

Section

• Open PR against RELEASE_ISSUE_TEMPLATE.md with title docs(release): v1.36.2 release template improvements for improving future releases.
  • Link to PR:
  • Open this as a draft PR and use it to collect release-process improvements discovered while running this checklist.
  • Suggested branch: docs/release-v1.36.2-template-improvements
  • This will get merged in a Post-Release step.
• Fork a new release/v1.36.2 branch from the master branch and make any further release-related changes to this branch.
  • For regular releases, use origin/master after confirming every Stable Release dependency above has landed.
  • Suggested commands:

    git fetch origin master --tags
    git push origin origin/master:refs/heads/release/v1.36.2
    git ls-remote --heads origin release/v1.36.2

  • Note: For critical security patches, fork a new branch from the last stable release/vX.Y.x to expedite the release process.

RCs

Section

• Skipped. This release issue uses the no-RC flow for a release with no related network upgrade.
• If release-owner review finds risk that needs soak time, regenerate or edit this issue with --release-flow=rc.

Stable Release

Section

[!IMPORTANT]
These PRs should be done in and target the relevant release branch for this issue.
Node branch: release/v1.36.2

Backport PR for Stable Release

• All explicitly tracked items from Dependencies for releases have landed
• Confirm there are no unresolved release/backport blockers unless they are intentionally deferred and linked here:
  • Deferred items:
• No additional backport PR is needed because this no-RC release branch was created from origin/master after dependency resolution.

Release PR for Stable Release

• Update the version string(s) in build/version.go to 1.36.2 (without a leading v).
  • Change NodeBuildVersion to 1.36.2
  • The release tags include the leading v; the values in build/version.go do not.
• Run make gen && make docsgen-cli to generate documentation
• Create a draft PR with title build: release Lotus Node v1.36.2
  • 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
  • After the draft release exists, copy the auto-generated release notes into the CHANGELOG.
    • Note: after a draft release exists, rerunning the release workflow preserves the existing draft release body. If editorial review changes release-note content in CHANGELOG, update the draft GitHub release body too before merge; the push-triggered publish step publishes that draft body.
    • Node release body: gh release view v1.36.2 --repo filecoin-project/lotus --json body -q .body
  • Perform editorial review (e.g., callout breaking changes, new features, FIPs, actor bundles)
  • Ensure no missing content when spot checking git history
    • Find the previous stable tag first:
      • Node: git tag -l 'v*' | grep -v '-' | sort -V -r | head -n 1
    • Example command looking at git commits: git log --oneline --graph PREVIOUS_TAG..HEAD
    • Example GitHub UI search looking at merged PRs into master, where YYYY-MM-DD is the previous stable release publish date: 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
  • Review and update the draft GitHub release body so it matches the CHANGELOG.
  • Update the PR with the commit(s) made to the CHANGELOG
• Confirm the release PR CI is green, including release asset generation.
• Confirm the release owner approves publishing this stable release.
• Confirm any security-advisory staging needed for this release has an owner and follows policy.
• 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

[!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 branch. Title it chore(release): cherry-pick v1.36.2 changelog back to master
  • Link to PR:
  • Node source branch: release/v1.36.2
  • 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 Release Setup 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!