← Back to changelog
Release v0.6.1

Pyvider 0.6.1: Clearer lifecycle and provider-name diagnostics

August 31, 2026 View GitHub release ↗

Pyvider 0.6.1 tightened two feedback loops that had made otherwise ordinary mistakes hard to diagnose.

Fixed

  • Lifecycle violations name the attribute. When a resource’s final state is not a valid refinement of its plan, the diagnostic now includes the attribute path already found by validation. Provider authors no longer have to isolate the field by trial and error.
  • name is canonical; provider_name remains an alias. Provider-name resolution now agrees with pyvider.toml and plating across [tool.pyvider], top-level [pyvider], and standalone pyvider.toml configuration. Existing projects using provider_name continue to work.
  • Working-directory pyvider.toml participates in name resolution. The file Pyvider loads by default is now also considered when choosing the provider’s install name, without requiring PYVIDER_CONFIG_FILE to point at it explicitly.
  • Install reports the name source. pyvider install says where the resolved provider name came from, or makes the fallback to the default name explicit.

See the Pyvider v0.6.1 release for the canonical release record.