failed to select a version for the requirement `handlebars = "^5.1.1"`
candidate versions found which didn't match: 5.1.0, 5.0.0, 5.0.0-beta.5, ...
https://docs.rs/handlebars/latest/handlebars/index.html does say for 5.1.1: This release has been yanked, go to latest version. I build debian packages for ubuntu and debian stable. 1.30.2 was fine but ran into this today.
Installing vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)
Updating crates.io index
error: failed to compile `vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)`, intermediate artifacts can be found at `/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3/target`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
Caused by:
failed to select a version for the requirement `handlebars = "^5.1.1"`
candidate versions found which didn't match: 5.1.0, 5.0.0, 5.0.0-beta.5, ...
location searched: crates.io index
required by package `vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)`
if you are looking for the prerelease package it needs to be specified explicitly
handlebars = { version = "5.0.0-beta.5" }
perhaps a crate was updated and forgotten to be re-vendored?
Originally created by @dionysius on GitHub (Feb 2, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4307
<!--
# ###
NOTE: Please update to the latest version of vaultwarden before reporting an issue!
This saves you and us a lot of time and troubleshooting.
See:
* https://github.com/dani-garcia/vaultwarden/issues/1180
* https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image
# ###
-->
<!--
Please fill out the following template to make solving your problem easier and faster for us.
This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them.
Remember to hide/redact personal or confidential information,
such as passwords, IP addresses, and DNS names as appropriate.
-->
### Subject of the issue
```
failed to select a version for the requirement `handlebars = "^5.1.1"`
candidate versions found which didn't match: 5.1.0, 5.0.0, 5.0.0-beta.5, ...
```
https://docs.rs/handlebars/latest/handlebars/index.html does say for 5.1.1: **This release has been yanked, go to latest version**. I build debian packages for ubuntu and debian stable. 1.30.2 was fine but ran into this today.
### Troubleshooting data
https://github.com/dionysius/vaultwarden-deb/actions/runs/7756133150
```
Installing vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)
Updating crates.io index
error: failed to compile `vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)`, intermediate artifacts can be found at `/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3/target`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
Caused by:
failed to select a version for the requirement `handlebars = "^5.1.1"`
candidate versions found which didn't match: 5.1.0, 5.0.0, 5.0.0-beta.5, ...
location searched: crates.io index
required by package `vaultwarden v1.0.0 (/__w/vaultwarden-deb/vaultwarden-deb/vaultwarden-1.30.3)`
if you are looking for the prerelease package it needs to be specified explicitly
handlebars = { version = "5.0.0-beta.5" }
perhaps a crate was updated and forgotten to be re-vendored?
```
GiteaMirror
added the bug label 2026-04-20 14:05:29 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dionysius on GitHub (Feb 2, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4307
Subject of the issue
https://docs.rs/handlebars/latest/handlebars/index.html does say for 5.1.1: This release has been yanked, go to latest version. I build debian packages for ubuntu and debian stable. 1.30.2 was fine but ran into this today.
Troubleshooting data
https://github.com/dionysius/vaultwarden-deb/actions/runs/7756133150
@BlackDex commented on GitHub (Feb 2, 2024):
Thanks. That is unfortunate.
Working on a fix now.