spiffe v0.16.0

This release includes breaking API and feature-flag changes that reduce unnecessary dependencies and standardize source configuration types.

Migration guide

• Replace workload-api-full with workload-api.
• Replace crate-root ReconnectConfig / ResourceLimits imports with the source-specific aliases:
  • X509ReconnectConfig
  • X509ResourceLimits
  • JwtReconnectConfig
  • JwtResourceLimits
• Replace JwtSource::get_jwt_svid(...) with JwtSource::fetch_jwt_svid(...).
• Replace JwtSource::get_jwt_svid_with_id(...) with JwtSource::fetch_jwt_svid_with_id(...).
• Construct resource limits and reconnect configs using the provided constructors, defaults, or builder methods instead of struct literals.

Breaking changes

• x509-source now enables only workload-api-x509; jwt-source now enables only workload-api-jwt.
• Removed the redundant workload-api-full feature.
• Removed unprefixed ReconnectConfig and ResourceLimits re-exports from the crate root.
• Marked source resource limit and reconnect config types as non-exhaustive.
• Renamed JWT SVID fetch methods from get_* to fetch_*.

Added

• Re-exported Certificate and PrivateKey at the crate root.
• Re-exported BundleSource and SvidSource at the crate root.

Included PRs

• #357 fix(spiffe): narrow source feature dependencies
• #358 feat(source): standardize source config re-exports
• #359 feat(source): make source config types non-exhaustive and add constructors
• #360 feat(jwt-source)!: rename get_jwt_svid accessors to fetch_*
• #361 feat(api): re-export common certificate and source types
• #362 feat(source)!: make reconnect config non-exhaustive
• #363 chore(release): spiffe 0.16.0 and bump dependent crates

Full Changelog: spiffe-0.15.1...spiffe-0.16.0