v1.6.9

Features:

• Support for shared-* specification in ZAP errata to force derived clusters to use data types from its parent
• Disco now places device type component sections in standard order

Fixes:

• Support numbers in conformance identifiers
• Remove erroneous provisionality warning for SDK test data types
• Generate separate CharacteristicEnum under Media Playback cluster in ZAP XML for backwards compatibility

v1.6.8

Adds support for identifiers with numerals in conformance expressions

v1.6.5

Fixes:

1. Validation of orphan choices on Element Requirements on Composed Devices was checking the conformance of the associated Device Type Requirement, rather than the conformance on the Element Requirement itself
2. The --exit-error-code flag was not returning an error code when parse errors did not actually log an error

v1.6.4

Fixes:

1. Sets isFabricSensitive on attributes in Zap XML

v1.6.3

Features:

1. Adds support for overriding quality and access in errata

v1.6.2

The primary change in this release is a shift to using the errata file to directly change the parsed object model; this is enabled by the overlay introduced in 1.6.

This release also removes the "reportable" quality from the Data Model XML.

v1.6.1

Initial release of v1.6 Alchemy.

Features:

• New parsing pipeline; slightly faster and more flexible.
  

Fixes:

• Removes no-longer-needed Descriptor cluster patch for ZAP XML generation
• Renders status code fields data type as "status" in ZAP XML, despite whatever the label on the reference says.
• Removes accidentally hard-coded version string in XML comment

v1.5.56

Adds "revision" element to device types in matter-devices.xml

v1.5.55

Features:

1. Disco-balling now alphabetizes the Quality column by default. Disable with --format-quality=false, or in errata with by skipping table-quality

Fixes:

1. Blank conformance cells no longer default to Mandatory in derived clusters.

v1.5.54

Fixes:

1. Empty final table cells were being treated as non-existent in RenderColumn, which caused inaccurate inheritance of cluster requirements in derived cluster element requirements
2. Cluster requirements in data model XML were being rendered in spec order, rather that a stable sort of cluster ID