deps: bump age from 0.11.4 to 0.12.1 in /src-tauri

[dependabot]

Bumps age from 0.11.4 to 0.12.1.

Release notes

Sourced from age's releases.

rage v0.12.1

rage

Fixed

• Armored files that contain an empty final line are now correctly rejected.

age

Fixed

• age::armor::ArmoredReader:
  • It now correctly implements the intended strict parsing profile (initially implemented in 0.9.0) by rejecting an empty final line.
  • The async API now correctly rejects some classes of truncated files that previously would cause it to hang.

rage v0.12.0

rage

Added

• Support for the new native age recipient types:
  • age1tag1..
  • age1tagpq1..

Changed

• MSRV is now 1.74.0.

age

Added

• Support for new native age recipient types:
  • age::tag::Recipient (encryption-only)
  • age::tagpq::Recipient (encryption-only)
• age::encrypted::EncryptedIdentity
• age::plugin::ResolveError

Changed

• MSRV is now 1.74.0.
• Migrated to base64 0.22, i18n-embed 0.16.
• age::IdentityFile::into_identities now returns Result<Vec<Box<dyn crate::Identity + Send + Sync>>, DecryptError> instead of Result<Vec<Box<dyn crate::Identity>>, DecryptError>. This re-enables cross-thread uses of IdentityFile, which were unintentionally disabled in 0.11.0.
• age::plugin:
  • The following methods now returns Result<Self, ResolveError>:
    • Identity::default_for_plugin
    • RecipientPluginV1::new
    • IdentityPluginV1::new
• All existing error enums nameable in the public API are now non-exhaustive:
  • age::{EncryptError, DecryptError}
  • age::IdentityFileConvertError
  • age::armor::ArmoredReadError
  • age::cli_common::ReadError
  • age::ssh::ParseRecipientKeyError
• Removed the following error enum variants:
  • age::DecryptError::MissingPlugin
  • age::EncryptError::MissingPlugin
  • age::cli_common::ReadError::MissingPlugin

age-plugin 0.7.0

... (truncated)

Commits

• 7a854c9 v0.12.1
• c5aeafe Merge branch 'rage-0.11.4' into release-0.12.1
• 55ab2e9 v0.11.4
• 717a2f5 Merge pull request #633 from str4d/age-0.11.5
• 7f29934 age 0.11.5
• e956b71 age: Fix hang in impl AsyncBufRead for ArmoredReader on truncated files
• d57b2f5 age: Reject whitespace within armored files
• aea5836 age: Update testkit test files
• cf76a65 age: Update testkit test files
• 95a5959 age: Update testkit test files
• Additional commits viewable in compare view

[Aleixenandros]

Holding this one back for a dedicated pass rather than merging it with the routine bumps.

age is the crate that does the end-to-end encryption of the sync blob (sync.rs), so a 0.11 → 0.12 major needs more than a green build: it requires verifying on-disk format compatibility — that a blob encrypted by 0.11 (scrypt passphrase recipient) still decrypts under 0.12 and vice-versa — or existing users' synced data could become unreadable after an update. The API also moved (secrecy bump), so the bump alone doesn't build cleanly (CI is red here).

Keeping the PR open as a reminder; it'll be picked up in its own release with round-trip encryption tests, alongside the other held-back major (TypeScript was already adopted separately).

[Aleixenandros]

Investigado: no se puede mergear todavía, y no es un problema de nuestro código — es un conflicto de dependencias dentro del propio árbol de age 0.12.1.

age 0.12 añade soporte para destinatarios post-cuánticos (age1tag1…), lo que tira transitivamente de ml-kem 0.2.1. Nuestro cliente SSH (russh) ya trae ml-kem 0.3.2 por su lado. Cargo solo puede resolver una versión del crate kem del que ambos dependen y unifica en kem 0.3.0.

El problema: el manifiesto de ml-kem 0.2.1 declara su dependencia como kem = "^0.3.0-pre.0" — se escribió contra un borrador preliminar de la API de kem 0.3.0 que cambió antes de la versión final. Al resolver ese rango contra el kem 0.3.0 estable ya publicado, ml-kem 0.2.1 recibe una API distinta de la que su código espera, de ahí los errores de traits (Decapsulate/Encapsulate) que fallan en las cuatro plataformas del CI.

No hay combinación de versiones en nuestro Cargo.toml que lo resuelva: cualquier kem que satisfaga a ml-kem 0.3.2 (russh) rompe a ml-kem 0.2.1 (age), y viceversa. Solo se arregla cuando age publique una versión que actualice su dependencia de ml-kem a la 0.3.x. Ahora mismo 0.12.1 es la última versión de age disponible, así que no hay nada que actualizar todavía.

Aparte de esto, sigue pendiente la comprobación original: age cifra de extremo a extremo el blob de sync, así que antes de mergear cualquier futura versión que sí compile habrá que verificar que un blob cifrado con la 0.11 se siga descifrando con la nueva antes de dar el bump por bueno.

Se deja abierta para que dependabot la reabra/actualice cuando age publique una versión compatible.