diff --git a/docs/reference/configuration/credentials/keepassxc.md b/docs/reference/configuration/credentials/keepassxc.md
index 80be581c..ca88cee8 100644
--- a/docs/reference/configuration/credentials/keepassxc.md
+++ b/docs/reference/configuration/credentials/keepassxc.md
@@ -62,7 +62,8 @@ keepassxc:
### Key file
-KeePassXC supports unlocking a database with a separate [key
+New in version 2.0.0KeePassXC
+supports unlocking a database with a separate [key
file](https://keepassxc.org/docs/#faq-keyfile-howto) instead of or in addition
to a password. To configure borgmatic for that, use the `key_file` option:
@@ -71,10 +72,10 @@ keepassxc:
key_file: /path/to/keyfile
```
-By default, keepassxc-cli prompts the user for the password to unlock a
-database. But if you only want to provide a key file to unlock your database and
-not a password, for instance to support unattended backups, use the
-`ask_for_password` option:
+New in version 2.0.12By default,
+keepassxc-cli prompts the user for the password to unlock a database. But if you
+only want to provide a key file to unlock your database and not a password, for
+instance to support unattended backups, use the `ask_for_password` option:
```yaml
keepassxc:
@@ -84,7 +85,8 @@ keepassxc:
### YubiKey
-KeePassXC also supports unlocking a database with the help of [a
+New in version 2.0.0KeePassXC
+also supports unlocking a database with the help of [a
YubiKey](https://keepassxc.org/docs/#faq-yubikey-2fa). To configure borgmatic
for that, use the `yubikey` option: