1.0.60

Fixed

• Neat now correctly classifies changing autoIncrement in a container
  property as a breaking change (before it was a warning).

1.0.59

Added

• Release

1.0.58

Fixed

• Fixes a crashing issue when reading Toolkit-format data models with
  version strings containing periods (e.g. 1.0.0).

1.0.57

Improved

• When reading data models from yaml, Neat now handles integer in the
  version field of views and data models.

1.0.56

Fixed

• When exporting from Neat to Toolkit,
  neat.physical_data_model.write.yaml(..., format="toolkit"), Neat no
  longer includes resources in system spaces, writes to a resoruce folder
  named data_modeling, and skips null values.

Improved

• To export Neat to Toolkit in directory format, for example,
  neat.physical_data_model.write.yaml("my_module" format="toolkit"),
  then the directory does not need to exist before calling the function.

1.0.55

Added

• Plugin discovery and loading via importlib.metadata.entry_points()
• Dynamic method generation from external plugins with signature
  preservation

1.0.54

Added

• [alpha] Alpha flag that enables you to govern containers/views in
  different spaces than the data model. This means Neat will allow you to
  deploy to these spaces as well as account for it in its validation.

1.0.53

Fixed

• Fixed SchemaDeployer.apply_changes() to properly mark skipped
  resources with current_value and new_value set to None when
  preceding resources fail during deployment.

1.0.52

Changed

• 🔄 Changed all data model limit validation rules to produce
  Recommendation instead of ConsistencyError, allowing attempting
  deployment even when CDF limits are exceeded.

1.0.51

Changed

• NEAT-DMS-LIMITS-CONTAINER-001 rule behavior