Next release

[Kijewski]

• feature freeze
• exchange https://github.com/rinja-rs/ and https://github.com/askama-rs/
• Rename rinja into askama #353
• update the readme and the book
• update readthedocs
• update oss-fuzz: Rename "rinja" into "askama" google/oss-fuzz#13127, ci: re-enable Cluster-Fuzz #376
• replace the readme on https://github.com/askama-rs/askama-old to redirect here, then archive the old repo: Archive the repository askama-old#1129
• Update https://github.com/askama-rs/play-rinja: Rinja is Askama, again askama_playground#26, Update askama_playground URL #368
• Update https://github.com/askama-rs/template-benchmark: Rinja is Askama, again template-benchmark#10
• do one or more pre-releases:
  1. Bump version number to v0.13.0-pre.0 #370
• ask some people to try the pre-release
• write a blog post to explain everything (@GuillaumeGomez) (https://blog.guillaume-gomez.fr/articles/2025-03-19+Askama+and+Rinja+merge)
• release askama v0.13.0
• Release rinja v0.3.6+deprecated #344
• Release rinja v0.4.0+deprecated #345
• archive the old askama project, redirecting users here
• (optional) try to help projects to migrate:
  • Update to askama 0.13.0 plotly/plotly.rs#281
  • https://codeberg.org/mo8it/oxitraffic/pulls/24
  • Migrate to askama 0.13.0 mozilla/uniffi-rs#2494

Am I missing something? Is this the right order?

[GuillaumeGomez]

I'd prefer if instead we simply renamed the repository into askama. After all we're a fork, so we still have askama git history and that will make things simpler since we don't need to migrate issues and PRs.

Also, I need write a blog post about all this. :)

[Kijewski]

Well, I guess it does not matter a lot. I would have liked the other route better, though, regardless if it is more complicated.

[GuillaumeGomez]

Less work for us. :D

[Kijewski]

I don't think there is anything that we need to include the next release, esp. there are no breaking changes I would like to include. @GuillaumeGomez, is there something you would like to include or can we call it a "feature freeze". :)

[GuillaumeGomez]

Sorry didn't see this message. Yes, time for feature freeze!

[Kijewski]

The project is https://github.com/askama-rs/askama/ again. 🎉

[GuillaumeGomez]

We should also update https://github.com/askama-rs/play-rinja repository.

[Kijewski]

@GuillaumeGomez, first pre-release tomorrow? What do you think? :)

[GuillaumeGomez]

Sounds all good to me, thanks for the work! I really need to write the blog post. ^^'

[GuillaumeGomez]

Blog post is now written. :)

[Kijewski]

[Kijewski]

I tried to categorize all PRs between v0.3.5 and v0.13.0-pre.0: https://github.com/askama-rs/askama/releases/tag/v0.13.0-pre.0. The order is roughly by date. @GuillaumeGomez, if you would like to put PRs in other categories / change the categories / reorder some or all PRs, feel free. :)

[GuillaumeGomez]

Wow, thanks for that! Looks all good to me. :)

[matze]

ask some people to try the pre-release

I tried. It was painless.

[Walter-Reactor]

Confirmed, I just tried uprevving diplomat from askama 0.12 & didn't find any changes I needed to make.

[Kijewski]

I guess there is no need to release rinja v0.3.6 with a deprecation message. The version is not broken, and if someone does not want to update for some reason, they don't have to. Then, I guess we're all done here. What do you say, @GuillaumeGomez? :)

(Hopefully we never have such a big release again, though :D)

[GuillaumeGomez]

Nah I don't think it's necessary. Our work here is done. Congrats!