-
Notifications
You must be signed in to change notification settings - Fork 280
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
Packaging issue with v1.0.0-alpha.0 #1657
Comments
Interesting. Thanks for reporting this! This might have started happening after the Does Rust's variation of semver automatically bump to |
sorry, this is not very clear, could you show us your |
I wasn't able to use I pushed it up here: https://github.com/abernix/repo-apollographql-router-issue-1657 |
@deweyjose so this is an unfortunate consequence of semver matching in Cargo: 0.1.0-alpha.0 is compatible with 0.1.0, and Cargo dependencies that only specify a version allow the upgrade to another compatible version. Since the scaffolded project does not come with a This will be fixed in the next router release, which should happen in the next few days. In the meantime, if you specify the dependency on the router to this commit or any more recent commit, it will compile properly |
We believe this will be fixed when #1689 releases, which should be in the next hour or so. Thanks for your patience! |
The Using my reproduction — which used the
|
thanks all! |
By default v1.0.0-alpha.0 does not compile. The dependency on router-bridge is incorrect - v0.1.0 instead of v0.1.0-alpha.1.
I updated my Cargo.toml to use
1v1.0.0-alpha.0
Projects generated by the apollo router scaffold also have this issue - v1.0.0-alpha.0 apollo-router depdencies with router-bridge v0.1.0 dependency.
I was able to work around this by updating the dependency manually:
cargo update -p router-bridge --precise 0.1.0-alpha.1
The text was updated successfully, but these errors were encountered: