-
Notifications
You must be signed in to change notification settings - Fork 17
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
Release tracking PR: v0.6.0
#49
base: master
Are you sure you want to change the base?
Conversation
f22905c
to
ac517db
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK ac517db; successfully ran local tests
0490471
to
a55fe9b
Compare
a55fe9b
to
894e1d9
Compare
894e1d9
to
f919d19
Compare
f919d19
to
691a6bd
Compare
Changelog for #79 added to |
691a6bd
to
2c2bd87
Compare
Rebased to pick up #74 |
2c2bd87
to
4007035
Compare
Added 1062193 |
Now I broke it. Its bizzare, I can get |
6918ac9
to
3e9376d
Compare
Hmm, do you happen to enable |
That explains my confusion yesterday I must have changed between running tests with v18 and later versions - then I couldn't work out why it worked at some stage. Thanks man, I was very confused by that. |
Add a brief readme file, point at `cargo run -- --help` and also at the docs we already wrote in `types/README.md`.
In preparation for release bump the version numbers of `types`, `client`, and `node` to `0.6.0`. Add changelog entries to each and update the lock files.
3e9376d
to
8a1883b
Compare
Will come back and do a quick final sweep of the crates while debugging this and before release. |
In preparation for release of all three crates add changelog entries, bump the version number, and update the lock files.
Patch 2 closes #69