Skip to content

Bump version #446

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

Merged
merged 6 commits into from
Jul 8, 2019
Merged

Bump version #446

merged 6 commits into from
Jul 8, 2019

Conversation

ascjones
Copy link
Contributor

@ascjones ascjones commented Jul 4, 2019

In preparation for a release to include the pubsub client #436.

@ascjones ascjones added the chores label Jul 4, 2019
@ascjones ascjones requested a review from tomusdrw July 4, 2019 15:34
Copy link
Contributor

@tomusdrw tomusdrw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@@ -8,7 +8,7 @@ keywords = ["jsonrpc", "json-rpc", "json", "rpc", "serde"]
license = "MIT"
name = "jsonrpc-core-client"
repository = "https://github.com/paritytech/jsonrpc"
version = "12.0.0"
version = "13.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need 13.0? Can't we just bump to 12.1? Are there any breaking changes?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If there is a bug in handling existing #[pubsub] macros it will break builds.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, but is there?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dvc94ch true but that would be an unintentional "breaking" change, the API itself should still be compatible.

@tomusdrw so core-client and derive should both go to 12.1 then.?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather keep all creates version aligned. So if we feel there is a reason to bump to 13.0 let's do that, but if there are no breaking changes that we know of, let's stick to 12.1 imho.

Copy link
Contributor Author

@ascjones ascjones Jul 4, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually there is also an addition to core https://github.com/paritytech/jsonrpc/pull/436/files#diff-77e9ef3aa593be6048a014ed42ef10dbR34

So upgrade all crates to 12.1?

Didn't see your message above. Will do 12.1

@ascjones ascjones changed the title Bump version (and fix script) Bump version Jul 4, 2019
@dvc94ch
Copy link
Contributor

dvc94ch commented Jul 8, 2019

So is this happening? :)

@ascjones
Copy link
Contributor Author

ascjones commented Jul 8, 2019 via email

@ascjones ascjones merged commit 584327b into master Jul 8, 2019
@tomusdrw tomusdrw deleted the aj-bump-version branch July 29, 2019 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants