Differences from 0.0.x

Pacts generated by 0.1.0 embed schema text that differs from 0.0.x output (no logicalType attributes, different key order), so the schemaKey changes. Regenerate and republish your consumer pacts after upgrading. Verifying pacts generated by 0.0.x still works, because the schema travels inside the pact.

Avro map fields encode their entries sorted by key in UTF-8 byte order, so the same map always produces the same bytes and republishing an unchanged pact does not show a change. Pacts generated by 0.0.x that contain a map with two or more entries can differ once from 0.1.0 output; regenerate them like the pacts described above.

Releases follow semantic versioning, computed from Conventional Commit subjects: a breaking change bumps the major version, a new feature the minor version, and a fix the patch version.