build(deps): bump age from 0.11.2 to 0.11.3 in /codex-rs

[dependabot]

Bumps age from 0.11.2 to 0.11.3.

Commits

• 681face age 0.11.3
• aa5b1d6 cargo vet prune
• f456910 Reformat audit files to match cargo-vet 0.10.2 format
• e97d2d7 CI: Switch to Go 1.24 for interop tests
• e3cf83d age: Limit SSH keys to 16 kiB
• 8e5145f age: Limit recipient and identity files to 16 MiB
• 6fe47a2 age: Add some zeroization to IdentityFile
• 85c747c age: Zeroize intermediate buffer when parsing x25519::Identity
• cd2e00d age: Replace file-key panics with errors in plugin::IdentityPluginV1
• fc4164f age: Fix panics on weird error formats in plugin responses
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[nuntius-review]

Vesper

Reviewed commits

Commit	Summary
8f034f0	build(deps): bump age from 0.11.2 to 0.11.3 in /codex-rs

The provided changes represent a routine dependency update for the age crate (a Rust implementation of the age file encryption format) from version 0.11.1 (resolved to 0.11.2 in the lockfile) to 0.11.3.

Analysis

• Correctness: The update is correct. The version specified in Cargo.toml (0.11.3) matches the resolved version and checksum in Cargo.lock.
• Security & Performance: Updating to the latest patch version (0.11.3) is a good practice as patch releases typically contain bug fixes, security hardening, and minor performance improvements without introducing breaking API changes.
• Compatibility: Since this is a patch-level update (following Semantic Versioning), it is fully backwards-compatible and safe to merge.

No changes or corrections are required.