Not much to look at here now haha.

But, we can already add the specific 2025.5.1 changes to Vaultwarden css though. You can use an if-else (webver >= 2025.5.1) for this. Also because maybe some users have an out-of-sync Vaultwarden<>Web-vault.

But, we can already add the specific 2025.5.1 changes to Vaultwarden css though. You can use an if-else (webver >= 2025.5.1) for this.

Just tested it and it doesn't work with my local version because the web-vault version in vw-version.json which is used to determine the version first is still v2025.5.0.

Manually changing it to v2025.5.1 works.

Shouldn't this have created a new release or did I misunderstand the process.

Only when i actually create it. For which i didn't had time to fully start it.

Only when i actually create it

What does that mean? Create what exactly? A tag? Or the github form at https://github.com/dani-garcia/bw_web_builds/releases/new?

Yes a tag indeed.

Thanks and sorry for my questions. I just wanted to understand the process because your second part "For which i didn't had time to fully start it." made me wonder.
Creating a tag takes 3 seconds and pushing the tag another second. Of course "drafting" a release via the github form takes more time, if you do it manually (creating the changelog, the release text, ...).
Even though I am not a project member I still like to understand the inner workings of a project, especially one I am very much interested in.

Well, i was working on other stuff. And merged this during a coffee break at my day job, and after that lost in other stuff. I'm a bit chaotic and multi-tasking all day long.

No, no. Please don't take this the wrong way. I understand that you are busy. I just wanted to understand the process. It'll be ready, when it's ready.

P.S.: I can build everyhing myself. I am not in need of official releases.