Skip to content
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

chore: releases: merge releases branch to master #11577

Closed
wants to merge 54 commits into from

Conversation

rjan90
Copy link
Contributor

@rjan90 rjan90 commented Jan 15, 2024

Proposed Changes

Need to resolve the conflicts. But last step of #11476, merging releases branch into master.

Checklist

Before you mark the PR ready for review, please make sure that:

  • Commits have a clear commit message.
  • PR title is in the form of of <PR type>: <area>: <change being made>
    • example: fix: mempool: Introduce a cache for valid signatures
    • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
    • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
  • If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
  • New features have usage guidelines and / or documentation updates in
  • Tests exist for new functionality or change in behavior
  • CI is green

rjan90 and others added 30 commits December 5, 2023 10:09
Initial draft changelog
Update changelog
Add sub-bullets to new features
chore: backport: lotus-provider msg sending fix
Fix changelog
Add backports to changelog
Also explicitly limit how many bytes we're willing to read in one go
such that we're capable of reading a worst-case tipset (like, really,
never going to happen worst-case). Previously, this wasn't an issue.
However, we've bumped the max number of messages from 8,192 to 150,000
and need to limit allocations somewhere else.
Also explicitly limit how many bytes we're willing to read in one go
such that we're capable of reading a worst-case tipset (like, really,
never going to happen worst-case). Previously, this wasn't an issue.
However, we've bumped the max number of messages from 8,192 to 150,000
and need to limit allocations somewhere else.
It's not a const for the testground build, and needs to be an int 99%
of the time. So we might as well just cast here.
It's not a const for the testground build, and needs to be an int 99%
of the time. So we might as well just cast here.
fix: lotus-provider: show addresses in log
fix: lotus-provider: Wait for the correct taskID
fix: lotus-provider: Fix log output format in wdPostTaskCmd
magik6k and others added 24 commits December 11, 2023 15:51
This reverts commit 3569e4e.
…-update-libp2p

chore:libp2p:update libp2p deps in release-v1.25.2
backports: lotus-provider: fixes caught in rc1-testing
feat: syncer: optimize syncFork for one-epoch forks
…post-err

fix: wdpost: fix vanilla proof indexes
chore: backports to `release/v1.25.2`
fix: docs: Modify generate-lotus-cli.py to ignoring aliases.
Bump version and changelog
Update changelog
Update changelog
feat: exchange: change GetBlocks to always fetch the requested number of tipsets
Update changelog with sync-fix-backport
Change date for release in changelog
chore: release: update changelog with latests backports
chore: merge `release/v1.25.2` into `releases`
@rjan90 rjan90 closed this Jan 15, 2024
@rjan90 rjan90 deleted the chore-releases-to-master branch January 15, 2024 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants