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

merge release/v1.20.1 into ntwk/hyperspace #10410

Merged
merged 84 commits into from
Mar 8, 2023

Conversation

raulk
Copy link
Member

@raulk raulk commented Mar 7, 2023

No description provided.

Shrenuj Bansal and others added 30 commits November 16, 2022 13:55
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
…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.
jennijuju and others added 24 commits December 12, 2022 22:51
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
* add upgrade epoch and bump version

* Update changelog

---------

Co-authored-by: Aayush <arajasek94@gmail.com>
@raulk raulk requested a review from a team as a code owner March 7, 2023 18:21
@raulk raulk merged commit 18dd645 into ntwk/hyperspace Mar 8, 2023
@raulk raulk deleted the raulk/merge-v1.20.1-into-hyperspace branch March 8, 2023 19:52
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.

10 participants