-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: release Lotus node v1.29.0 #12422
Conversation
build: release v1.29.0
changelog needs some attention, first it's not rendering quite right in the Secondly it's missing stuff in the changelog, was that generated correctly? I went looking for 4cf5ca6 because I thought it at least worth noting here that we are knowingly releasing #12272 and will fix the historical drand lookups in 1.29.1. Using `branch-diff` to make it it looks like this:
|
fix: add line break before H3
fix: update changelog with missing entries
fix: update reference to correct PR number
Went through the whole branch-diff now, and added missing entries in 8d23ee2. There is a lot of interesting cases in this diff as well, which might be worth spending some time bike shedding on how we should handle? (I did not add these to the sorted changelog): Backported to other releases:
How should we handle Lotus-Miner related PRs/Commits in the changelog for Lotus Node only releases:
Stacked PRs / Closed PRs pulled into other PRs
Rebase merged PRs / commits covered by
I get 404s on these PR numbers??
Since we have now moved to building the changelog incrementally, I'm not sure what value the "sorted changelog" actually brings in value. At least from a time consumption perspective, just adding a link of the diff to previous release will save a lot of time: v1.28.2...release/v1.29.0. |
Thanks for digging!
Looking at a few of these, I think this is as a result of squash merging or squashing on a merge-back, so we lose the individual commits. One of the reasons we should avoid squashing big batches of commits I think.
I think .. going forward, when we branch from
Bugs in matching the commit to the PR. I know GitHub does a decent job of mapping commit to PR these days so I wonder if there's a new API I could build in to branch-diff to do this properly. It currently uses a fall-back best-guess method to figure it out if you don't have a
User was deleted and so were their PRs! PR is properly referenced by GitHub: 7ea0e6c but it links to a 404. But as does user: https://github.com/fsgerse - one of the downsides of accepting these tiny PRs that look like someone just fishing for airdrop cred. But the commits themselves look OK from this user. |
fix(release): update date in changelog
fix: add upgrade warning about historic `StateGetBeaconEntry`
👍 for 65e5fba |
* build: release v1.29.0 build: release v1.29.0 * fix: add line break before H3 fix: add line break before H3 * fix: update changelog with missing entries fix: update changelog with missing entries * fix: update reference to correct PR number fix: update reference to correct PR number * fix(release): update date in changelog fix(release): update date in changelog * fix: add upgradedwarning about historic `StateGetBeaconEntry` fix: add upgrade warning about historic `StateGetBeaconEntry`
* build: release v1.29.0 build: release v1.29.0 * fix: add line break before H3 fix: add line break before H3 * fix: update changelog with missing entries fix: update changelog with missing entries * fix: update reference to correct PR number fix: update reference to correct PR number * fix(release): update date in changelog fix(release): update date in changelog * fix: add upgradedwarning about historic `StateGetBeaconEntry` fix: add upgrade warning about historic `StateGetBeaconEntry`
* build: release v1.29.0 build: release v1.29.0 * fix: add line break before H3 fix: add line break before H3 * fix: update changelog with missing entries fix: update changelog with missing entries * fix: update reference to correct PR number fix: update reference to correct PR number * fix(release): update date in changelog fix(release): update date in changelog * fix: add upgradedwarning about historic `StateGetBeaconEntry` fix: add upgrade warning about historic `StateGetBeaconEntry`
* build: release Lotus node v1.29.0-rc1 (#12410) * build: release v1.29.0-rc1 Bump version to v1.29.0-rc1 and make gen / make docsgen-cli * chore: update changelog for v1.29.0-rc1 chore: update changelog for v1.29.0-rc1 * chore: add link for more context Co-authored-by: Steve Loeppky <[email protected]> * chore: update sentence Co-authored-by: Steve Loeppky <[email protected]> * Update CHANGELOG.md Co-authored-by: Steve Loeppky <[email protected]> * chore: add emoji in heading Co-authored-by: Steve Loeppky <[email protected]> * Update CHANGELOG.md Co-authored-by: Steve Loeppky <[email protected]> * Update CHANGELOG.md Co-authored-by: Steve Loeppky <[email protected]> * Update CHANGELOG.md Co-authored-by: Steve Loeppky <[email protected]> * Update CHANGELOG.md Co-authored-by: Steve Loeppky <[email protected]> * Update CHANGELOG.md Co-authored-by: Steve Loeppky <[email protected]> * Update CHANGELOG.md Co-authored-by: Steve Loeppky <[email protected]> --------- Co-authored-by: Steve Loeppky <[email protected]> * build: release Lotus node v1.29.0 (#12422) * build: release v1.29.0 build: release v1.29.0 * fix: add line break before H3 fix: add line break before H3 * fix: update changelog with missing entries fix: update changelog with missing entries * fix: update reference to correct PR number fix: update reference to correct PR number * fix(release): update date in changelog fix(release): update date in changelog * fix: add upgradedwarning about historic `StateGetBeaconEntry` fix: add upgrade warning about historic `StateGetBeaconEntry` --------- Co-authored-by: Steve Loeppky <[email protected]>
#12343
Proposed Changes
Prep v1.29.0 stable release
Checklist
Before you mark the PR ready for review, please make sure that: