Skip to content

docs(release): v1.34.0. v1.34.1, v1.34.2 release template improvements#13270

Draft
BigLep wants to merge 2 commits into
masterfrom
docs/release-template-improvements-v1.34.0
Draft

docs(release): v1.34.0. v1.34.1, v1.34.2 release template improvements#13270
BigLep wants to merge 2 commits into
masterfrom
docs/release-template-improvements-v1.34.0

Conversation

@BigLep
Copy link
Copy Markdown
Member

@BigLep BigLep commented Aug 18, 2025

Summary

  • Remove "major" release level option from release CLI since we don't have special logic for major releases and have never done a major version release
  • Add "(nv$networkVersion)" suffix to GitHub issue titles when a network upgrade version is specified
  • Minor whitespace cleanup to release template

This PR will be used to collect incremental improvements during the v1.34.0 release process as recommended in the release template.

Changes that need to be made

  • Document more of the changelog prep commands like build: release Lotus Node and Miner v1.34.0-rc1 #13314 (comment)
  • Document about copy/pasting changelog back into the release itself
  • Document about how to handle changelog entries for new RCs
  • Is there any guide about the kind of content to have for things like the migration section of the changelog?
  • Document when the draft RC release gets triggered
  • When dealing with the node and miner release, we don't list commands about cherrypicking commits across to the miner branch.
  • Manual release GitHub workflow should default to ["node", "miner"] so it's more obvious what to put in there when running the workflow manually
  • We should update the template so that it's clear that the "before RC1" tasks need to be done even if not doing an RC
  • Final release should make sure using final releases of go-state-types, filecoin-ffi and that actors CIDs don't change.
  • For network upgrades, also need to update the network name like fix: update nv27 naming #13318

Outdated or not a priority

Changes Made

  1. Release Script (cmd/release/main.go):

    • Removed "major" from allowed release levels (now only "minor" and "patch")
    • Updated validation logic to exclude "major" releases
    • Added network version suffix to GitHub issue titles when network upgrade is specified
  2. Release Template (documentation/misc/RELEASE_ISSUE_TEMPLATE.md):

    • Added trailing newline for consistency

🤖 Generated with Claude Code

BigLep and others added 2 commits August 18, 2025 08:48
Add newline at end of file for release template improvements tracking.
This PR will be used to collect incremental improvements during the
v1.34.0 release process as recommended in the release template.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
…issue titles

1. Remove "major" release level option since we don't have special logic
   for major releases and have never done a major version release
2. Add "(nv$networkVersion)" suffix to GitHub issue titles when a
   network upgrade version is specified

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
rjan90
rjan90 previously approved these changes Aug 18, 2025
@github-project-automation github-project-automation Bot moved this from 📌 Triage to ✔️ Approved by reviewer in FilOz Aug 18, 2025
@rjan90
Copy link
Copy Markdown
Contributor

rjan90 commented Aug 18, 2025

Ah, I thought this PR was only for the release scripts improvements. But this might also encompass more findings when developing the v1.34.0 release. I will therefore dismiss my review until it goes out of draft

@rjan90 rjan90 dismissed their stale review August 18, 2025 16:06

Waiting till it is going out of draft

@BigLep BigLep mentioned this pull request Sep 16, 2025
22 tasks
@BigLep BigLep changed the title docs(release): v1.34.0 release template improvements docs(release): v1.34.0 and v1.34.1 release template improvements Sep 17, 2025
@rjan90
Copy link
Copy Markdown
Contributor

rjan90 commented Nov 24, 2025

With the v1.34.1 release published, I think this is now ready for review/merging?

@BigLep
Copy link
Copy Markdown
Member Author

BigLep commented Nov 24, 2025

With the v1.34.1 release published, I think this is now ready for review/merging?

I haven't reviewed/handled the items in "Changes that need to be made" yet. I'd like to tackle at least some of them before merging.

@BigLep BigLep changed the title docs(release): v1.34.0 and v1.34.1 release template improvements docs(release): v1.34.0. v1.34.1, v1.34.2 release template improvements Dec 1, 2025
@rjan90 rjan90 self-assigned this May 6, 2026
@BigLep BigLep moved this from ✔️ Approved by reviewer to ⌨️ In Progress in FilOz May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ⌨️ In Progress

Development

Successfully merging this pull request may close these issues.

2 participants