chore: merge releases into master #10377
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Aayush Rajasekaran <arajasek94@gmail.com>
…-binaries backport: Forgot to include linux binaries in goreleaser
Co-authored-by: Aayush Rajasekaran <arajasek94@gmail.com>
…19.0-rc1 chore: Update changelog for v1.19.0-rc1
Goreleaser checks to make sure we don't have a dirty git state when releasing, which means the kubo download we use to set up IPFS should be removed before release.
Without this name, it assumes all binaries share the name of the project (i.e. lotus), which causes them all to get renamed and collide when generating the archive.
This will give us much more detailed information in the release job, so we can more easily debug issues when they occur.
…easer baackport: ci: Fix issues with new goreleaser flow
I updated us to an intermediate version based on a git sha. That version removed a deprecation warning, but caused issues on older versions of MacOs (Big Sur and lower). This release of Zondax/hid fixes things in a way that both removes the deprecation warning and works on older MacOS versions.
backport: configurable pre check timeouts and zondax hid update
…sion_update Update build version and changelog
Update CHANGELOG.md
…kport chore: deps: update go-state-types backport
We have this env varible set in the project settings as well as the CircleCI context. Due to what seems like a bug on CircleCI's eng, the using the context causes our release flow to halt when some member of the team initiate releases, but not others. So for now, it's safest to rely on the project settings, which definitely won't cause this issue.
build: release: v1.19.0
feat: shed: test the nv18 migration
* add itests for various fevm block properties and assert correct chain id * add value checks to the block property solidity itests * move get block function to kit
chore: release v1.20.0-rc2
This will make `lotus send` mostly just "do what the user wants" in this case: 1. The user may not explicitly specify a method number. 2. Parameters are automatically cbor-encoded where applicable. 3. The method number is automatically selected based on the recipient (CreateExternal if sent to the EAM, InvokeEVM otherwise).
feat: gas: overestimate around the Hygge upgrade
fix: cli: send with InvokeEVM when sending from an eth account
chore: deps: update to go-state-types v0.10.0
fix: EthGetBalance: lookup balance at correct state
chore: deps: update to FFI v1.20.0
chore: deps: update to actors v10.0.0
* add upgrade epoch and bump version * Update changelog --------- Co-authored-by: Aayush <arajasek94@gmail.com>
build: release: v1.20.0
arajasek
force-pushed
the
asr/merge-release-into-master
branch
from
86a3915
to
19f1ad2
Compare
4 tasks
Stebalien
approved these changes
Mar 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issues
Last step of #10347
Proposed Changes
Additional Info
Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>fix: mempool: Introduce a cache for valid signaturesPR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, testarea, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps