Skip to content

[breaking change] use cargo --message-format for generating json errors #67

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 2 commits into from
Nov 19, 2016

Conversation

oli-obk
Copy link
Contributor

@oli-obk oli-obk commented Nov 18, 2016

fixes #65

we can simply do a major version bump and nothing should break for ppl who didn't update their cargo (I hope atom does semantic versioning).

cc @excaliburHisSheath

r? @alygin

@alygin
Copy link
Collaborator

alygin commented Nov 19, 2016

The fix looks good

@oli-obk oli-obk merged commit 2683fe0 into master Nov 19, 2016
@oli-obk oli-obk deleted the cargo_message_format branch November 19, 2016 18:34
@oli-obk
Copy link
Contributor Author

oli-obk commented Nov 19, 2016

published new version... we are now 1.0 xD

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.

Building triggers all dependencies to be rebuilt when building from the terminal
2 participants