-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
0.12 release planning #722
Comments
Thanks for pinging me. If you need help on something, don't hesitate to ask me! |
Hi, any update on the release? Is something holding it back? |
I guess the next step is to write up release notes. |
I was going through the book when I saw the version was still 0.8. This commit ensures all references to Askama version are to 0.11.2. Most of them already were. Merge whenever appropriate for release, djc#722 related
I was going through the book when I saw the version was still 0.8. This commit ensures all references to Askama version are to 0.11.2. Most of them already were. Merge whenever appropriate for release, #722 related
Any news about a new release? I currently use git but a release would be much appreciated :) The last one is from 2021. Thanks! |
I've drafted some release notes, any feedback? 0.12.0After 13 months of development, we're happy to announce the 0.12.0 release of Askama, the type safe, compiled Jinja-like template engine for Rust. For this release, @Kijewski contributed most of the changes -- @vallentin and @djc are the other team members. This releases comes with integrations for Actix-Web 4, Axum 0.6, Gotham 0.7, hyper 0.14, Tide 0.16 and Warp 0.3. We removed our Iron integration, since this framework no longer seems to be actively maintained. Features
Removed
Fixes
Documentation
Internal improvements
|
👍 |
Thank you! Looks good to me! |
Note the title of #677 does not appear accurate, might be worth correcting for the release notes? |
Why do you not think it's accurate? |
I've released it. |
The PR is titled "Merge askama_derive into askama" but it appears to be about merging |
Fair enough, I changed the title in the release notes. |
@GuillaumeGomez is asking when we can next release. Is there anything still in flight that we should merge first?
I know there's i18n (#700) which would be nice to move forward, but (a) that feels like it still needs a bunch of work, (b) it's maybe not breaking compat? Looks like we should also merge #632, potentially #668.
@Kijewski @vallentin any thoughts?
The text was updated successfully, but these errors were encountered: