unstale

pypi / azure-keyvault-keys

azure-keyvault-keys

What changed in azure-keyvault-keys 4, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-24.

26 breaking2 security3 new APIs and options1 behavior and defaults2 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.5 on npm

azure-keyvault-keys 434 changes

Breaking changes 26

  • Request URLs containing backslashes in the authority are rejected before authentication.

    4.11.3release notes

  • The minimum required cryptography version is now 44.0.2.

    4.11.1release notes

  • The sync method and async delete_key now return pollers that return a DeletedKey.

    4.0.0release notes

  • The method now has one positional parameter, name; optional parameters moved into kwargs.

    4.0.0release notes

  • The method now has positional parameters name and key_type; optional parameters moved into kwargs.

    4.0.0release notes

  • The method now has one positional parameter, name; optional parameters moved into kwargs.

    4.0.0release notes

  • Operations return class instances instead of tuples.

    4.0.0release notes

  • Removed this method from CryptographyClient.

    4.0.0release notes

  • The decrypted_bytes property was renamed to plaintext.

    4.0.0release notes

  • The sync method was renamed to begin_delete_key.

    4.0.0release notes

  • The async method now returns a poller that returns a DeletedKey.

    4.0.0release notes

  • The method now has positional parameters name and key; optional parameters moved into kwargs.

    4.0.0release notes

  • Renamed this class to KeyVaultKey.

    4.0.0release notes

  • The vault_endpoint parameter was renamed to vault_url.

    4.0.0release notes

  • Removed this method from KeyClient.

    4.0.0release notes

  • The created property was renamed to created_on.

    4.0.0release notes

  • The expires property was renamed to expires_on.

    4.0.0release notes

  • The updated property was renamed to updated_on.

    4.0.0release notes

  • Renamed this method to list_properties_of_key_versions.

    4.0.0release notes

  • Renamed this method to list_properties_of_keys.

    4.0.0release notes

  • Renamed this class to UnwrapResult.

    4.0.0release notes

  • The unwrapped_bytes property was renamed to key.

    4.0.0release notes

  • The method now has positional parameters name and optional version; other optional parameters moved into kwargs.

    4.0.0release notes

  • The vault_endpoint property was renamed to vault_url in all models.

    4.0.0release notes

  • The result property was renamed to is_valid.

    4.0.0release notes

  • Renamed this class to WrapResult.

    4.0.0release notes

Security 2

  • Cached challenges are verified before token use, and rejected or malformed entries are cleared without removing newer entries installed concurrently.

    4.11.3release notes

  • The authentication challenge is cached only after its resource is verified, preventing rejected challenges from being cached and reused by subsequent requests.

    4.11.2release notes

New APIs and options 3

  • Added support for service API version 2025-07-01.

    4.11.1release notes

  • All CryptographyClient returns now include an algorithm property.

    4.0.0release notes

  • All CryptographyClient returns now include a key_id property.

    4.0.0release notes

Behavior and default changes 1

  • Key Vault API version 2025-07-01 is now the default.

    4.11.1release notes

Fixes and other changes 2

  • Redirect header updates and cleanup are preserved when request bodies are restored during authentication.

    4.11.3release notes

  • When a 401 response omits this header, stale request authorization is removed and the observed cached challenge is cleared without retrying authentication.

    4.11.3release notes