-
Notifications
You must be signed in to change notification settings - Fork 251
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: release v5.0.0-alpha.1 #1070
Conversation
I love release-plz! I plan to cut 5.0.0-alpha.1 release and a couple of more releases before final 5.0.0. P.S. Hmm, CI fails due to changes in Cargo.locks in examples (where |
7cbe80b
to
160744f
Compare
This looks amazing! |
Just a reminder to tick off this list before the final |
c2196b5
to
7d91f80
Compare
7d91f80
to
f23bbb0
Compare
f23bbb0
to
64a9155
Compare
4a70fd7
to
a169fb2
Compare
691163b
to
1a883f1
Compare
9f615d7
to
5a607fd
Compare
Just to clarify, this is an automated PR created by release-plz, I plan to turn it into 5.0.0-alpha.1 release. |
42d08de
to
ffe042f
Compare
ffe042f
to
85dac05
Compare
85dac05
to
851edd8
Compare
Signed-off-by: Vlad Frolov <304265+frol@users.noreply.github.com>
851edd8
to
c6a1551
Compare
5397973
to
30eacb2
Compare
I don't know what is the issue with "buildkite/contract-builder", and I don't have access to view the logs, so I plan to ignore it. |
🤖 New release
near-sdk
: 4.1.1 -> 5.0.0 (near-sdk-macros
: 4.1.1 -> 5.0.0near-sys
: 0.2.0 -> 0.2.1 (✓ API compatible changes)near-contract-standards
: 4.1.1 -> 5.0.0 (✓ API compatible changes)near-sdk
breaking changesChangelog
near-sdk
near-sys
near-contract-standards
This PR was generated with release-plz.