Rocket v0.5-rc.1 is Available!

[SergioBenitez]

🚀 Rocket v0.5-rc.1 is Available!

Rocket 0.5.0-rc.1, a release candidate for Rocket v0.5, is now available!

This release actualizes over two years of development, bringing Rocket to Rust stable and async to Rocket. Every facet, from core request handling to error messages, has been subjected to Rocket's exacting standards. See the release announcement for more.

A general release is now imminent, but we need your feedback to make it happen. Please take the release candidate for a spin! We encourage all users to upgrade their applications to the release candidate. If you find an issue with the release, please let us know by posting on the issue tracker. For any general questions, concerns, or comments, feel free to respond to this discussion or, when appropriate, open a new discussion.

We hope you enjoy Rocket v0.5 as much as we enjoyed creating it!

[jlshattuck]

Hi Sergio - I'm getting a 404 on the issue tracker link https://github.com/SergioBenitez/Rocket/issue

[jlshattuck]

Looks like it's just missing the trailing "s" in issues

[SergioBenitez]

Thanks! Looks like this is just an issue on the discussion post. Fixed the link. :)

[jplatte]

What about rocket-contrib? Seems like the 0.5.0-rc.1 version didn't get published on crates.io

[jplatte]

Nevermind, was fooled by there still being a contrib dir at the repo root, rocket_dyn_templates and rocket_sync_db_pools have been released 👍🏼

[jebrosen]

Features from rocket_contrib crate have been merged into rocket, and/or split out into the new crates rocket_dyn_templates and rocket_sync_db_pools

[williamdes]

This is really awesome !! 👏🏻
I migrated my project that I am starting (folks searching for code examples): air-balloon/api@ed3f408
And migrated back to Rust stable (Docker multi stage using Alpine): air-balloon/api@f57d66a

Thank you so much for Rust stable support, this will help a lot with simpler configs 👍🏻

It also feels cleaner on Cargo.toml

Other migration example: mountains/permafrost@e7b5476

[JockeTF]

Awesome! Thanks a ton for this incredible framework!

[jplatte]

Two things I noticed while porting turbo.fish that might not be by design / should probably be called out in the migration guide:

• You can no longer have a module and a route handler named the same thing.
• ROCKET_ADDRESS no longer allows a value of localhost (not sure why I was using it like that, but it used to work, now Rocket fails to start instead)

[jebrosen]

You can no longer have a module and a route handler named the same thing.

Good catch. I assume this is due to structs (generated by codegen) sharing the same namespace as modules, and it definitely deserves a spot in the CHANGELOG/guide.

ROCKET_ADDRESS no longer allows a value of localhost (not sure why I was using it like that, but it used to work, now Rocket fails to start instead)

Yes, only an actual IP address is now supported. In 0.4 localhost was accepted (I assume any hostname that resolved to a local IP also works). This difference should be mentioned in the CHANGELOG, assuming we keep this restriction.

[imbolc]

Only a week for testing the RC? Even being on the the master branch, I pulled a couple of moths ago, took me 2 hours to refactor my 8 routes :) Updating FromRequest for auth and FromFormField for chrono types etc. Everything looks better btw :) But I'm afraid people from 0.4 won't have time to migrate and provide their feedback.

[SergioBenitez]

I think you raise an excellent concern. Perhaps an RC2 with a full migration guide would give users the support and time to migrate. I'll seriously consider this.

[williamdes]

migration guide: #1672 (reply in thread)

[TQLeung]

how can i update the rocket v0.4.7 to v0.5.0-rc1?? have link to guide??

[blackghost1987]

From the site: "A complete migration guide and news article will accompany the general release. Until then, the CHANGELOG contains every feature addition, change, and improvement since v0.4."

https://github.com/SergioBenitez/Rocket/blob/v0.5.0-rc.1/CHANGELOG.md

[memoryruins]

A migration guide was published a few days ago ^^
https://rocket.rs/master/guide/upgrading-from-0.4/

[blackghost1987]

I just wanted to say I managed to upgrade my application to v0.5-rc.1 without any major issues, thanks for all the information in the Changelog, it was really helpful 👍
Just one comment: I would emphasize the Contrib Graduation a bit more, maybe move it up in the guide, because it was not really clear to me at first how parts of the contrib crate was moved and/or separated into other crates. I've also expected features which have been included in Rocket (like "json") to be usable right away, but it turned out I have to add a feature tag in the Cargo.toml to enable them, that maybe worth a mention too.

Also I know it's a major aspect of v0.5 to be able to build on stable, which is great, but it might be wise to indicate that it's not mandatory. Some of the applications use nightly features anyway (sometimes even without the developer realizing it), or maybe the infrastructure change would be hard. For me it was much easier to first migrate all my stuff to v0.5-rc.1 without changing to stable, and later on change to stable separately.

[cmayoros]

Just curious, but this announcement was posted on June 9th. The official announcement on the website says the general release for 0.5 is planned for June 18th. It's August now, and it hasn't been released. What's going on?

[SergioBenitez]

It's been an unimaginably difficult month for me, personally, making it difficult to engage outside of these personal matters. Time brings recovery, and so I am certain to make progress on a release imminently.

[cmayoros]

I understand. Thanks for the updates. The software can wait, take care of what you need to.

[xamgore]

@SergioBenitez is there anything the community could help you with?

[commandline-be]

I hope things worked out by now, regardless my delayed yet not postponed sympathies.

[Razican]

I would love to see compression as part of the Rocket repository. Even if https://github.com/Ameobea/rocket_async_compression exists, having it as part of the usual Rocket distribution would help making it easier to implement.

[somehowchris]

Don't know why Ameobea used tokio as a dependency but just forked it and added some stuff https://github.com/somehowchris/rocket_async_compression

[somehowchris]

Well got merged back into https://github.com/Ameobea/rocket_async_compression

[somehowchris]

@SergioBenitez I hope you are doing fine and I really do not want to be rude, but is the project still on going? There are things left just like they were on the 24th of August and havent been touched, there are PRs & issues open. If I can help you out with something let us/me know

Would really hate to see such an amazing project not being developed and maintained

[Razican]

As far as he wrote, there were personal contingencies that prevented him from working in the project. We should give him some slack.

In any case, maybe it would make sense to have more maintainers in the future so that the project doesn't only depend on one person.

[somehowchris]

Indeed and as far as I know the last few months before vanishing he got some other people involved but they left.

Yes I saw his messages but he also wrote a few days ago in another topic that he will post news soon

[somehowchris]

Having a repository with over 1k forks and then having to search for a maintained fork is just not the solution to go for but on the other hand projects like Noria get put down as soon as the maintainer "finished" the task which were in his interests and didn't look for maintainers

[daniel-samson]

is there a roadmap for the 0.5 release? What is blocking the release?

[blackghost1987]

The only crate maintainer (Sergio) is not available for some time now for personal reasons, and we don't know where will he be back. The earliest he might be back is in the summer, so an 0.5 release is unlikely for a while.
We are trying to move the crate to a new GitHub organization (https://github.com/rocket-org/) to give more people release rights, see the discussion here: #2011

It's possible the organization can orchestrate a 0.5 release sooner, but if Sergio won't explicitly give release rights to the Org, then the release will have to be a new crate in Crates.io unfortunately

[daniel-samson]

I hope that it doesn't come to that. Rocket is awesome!!! I hope @SergioBenitez that you can come back or look for a maintainer to help out.