Replies: 1 comment 1 reply
-
|
I think we can start migrating to 0.6 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
On a new project I started, I decided to switch to the development channel of Rocket, giving me access to the v0.6 functionality.
While I'd normally be fine on stable, a key feature - HTTP/3 support - is not going to be backported, and with all the other changes coming in v0.6, I decided to just switch over now to avoid porting issues later.
However, upon adding SeaORM in, I had unexplained compiler errors - until I dug further. SeaORM is pegged to v0.5.1 and cannot, even with
crates.iopatches, be overridden past that. Not that it would work anyways, as it uses aninfo_!macro that no longer exists in v0.6.For now, I've created a minimal patch fork, which overrides Rocket to a particular mainline revision: amyipdev/sea-orm@48aa4ce
And for anyone who needs it, to import it in Cargo.toml:
Beta Was this translation helpful? Give feedback.
All reactions