What's Changed

• fix(composite): return error on truncated unknown TLV value instead of panicking (#415) by @SAY-5 in #416
• test(fuzz): add native Go fuzzers for Unpack/Pack and MessageScanner by @adamdecaf in #425
• ci(fuzz): anchor -fuzz patterns to avoid multi-match failures by @adamdecaf in #428
• fix(specs): register missing field types and encodings in the spec builder by @andresantoniuk in #430
• fix(composite): bounds-check unknown TLV length in skip path by @SashaMIT in #427

New Contributors

• @SAY-5 made their first contribution in #416
• @andresantoniuk made their first contribution in #430
• @SashaMIT made their first contribution in #427

Full Changelog: v0.26.0...v0.26.1

What's Changed

• fix: support TagSpec TLV fields in JSON export/import by @alovak in #408
• feat: add YAML serialization/deserialization for message specs by @alovak in #409
• feat: add support for re-marshaling unknown TLV tags in MarshalPath by @MassimilianoPoggiQonto in #412
• feat: add MessageScanner for partial message parsing by @alovak in #413

New Contributors

• @MassimilianoPoggiQonto made their first contribution ❤️ in #412

Full Changelog: v0.25.3...v0.26.0

What's Changed

• feat: add UnknownTags helper function to get skipped unknown tags by @alovak in #405

Full Changelog: v0.25.2...v0.25.3

What's Changed

• Support composites with optional repeating fields by @gyrolc in #398

New Contributors

• @gyrolc made their first contribution in #398

Full Changelog: v0.25.1...v0.25.2

What's Changed

• allow preserving unknown fields instead of discarding them by @alovak in #397

Full Changelog: v0.25.0...v0.25.1

What's Changed

• allow preserving unknown fields instead of discarding them by @alovak in #393
• Fix getters by @alovak in #396

⚠️ Breaking Changes

GetField() now returns nil for unset fields: GetField(id) returns nil if the field is not set or not defined in the specification, whereas previously it always returned a field instance.

Migration:

• Add nil checks before using the returned field
• Or migrate to GetString(id) / GetBytes(id) which handle nil safely and return zero values for unset fields

This change aligns with the new lazy field loading behavior and makes field presence checking explicit. It fixes the issue introduced in v0.24.0 where getting the value of a field that wasn't set was setting it.

Full Changelog: v0.24.0...v0.25.0

What's Changed

Lazy load field by @alovak in #392

Performance Improvements

Lazy field loading delivers significant performance gains:

Fields are now created on-demand rather than pre-allocated from the specification. Only fields actually used in a message consume memory.

In production scenarios where specs define many more fields than individual message types use, improvements across all metrics can exceed 80%.

Features

• Lazy field instantiation: Fields are created only when needed via internal getOrCreateField() and createField() methods
• New Instantiator interface: Allows custom field types to define their own instantiation logic via NewInstance() method

⚠️ Breaking Changes

1. Partial unpacking on failure: When unpacking fails on a field, that field is now created on the message/composite with its zero value, whereas previously it wasn't created at all. This allows partial data recovery but changes behavior for error handling code that checks field presence.

2. Error message changes: Several error messages have been updated for clarity:

   • "field X does not exist" → "field X is not defined in the spec"
   • "no specification found" → "is not defined in the spec"
   • Error messages now include additional context

3. Removed exported APIs:

   • CompositeWithSubfields interface
   • ConstructSubfields() method on Composite
   • CreateSubfield() function
   • CreateSubfields() function

Full Changelog: v0.23.5...v0.24.0

What's Changed

• Marshal unmarshal by path by @alovak in #391

Full Changelog: v0.23.4...v0.23.5

What's Changed

• fix: a binary field can marshal to a named string by @Inuart in #371
• docs: clarify composite spec.Legth by @alovak in #360
• docs: clarify usage DisableAutoExpand of the Bitmap field spec by @alovak in #368

Full Changelog: v0.23.3...v0.23.4

What's Changed

• docs: rework, reorg and improve readme by @alovak in #345
• fix(deps): update module golang.org/x/text to v0.22.0 by @renovate in #347
• fix: DecodeLength() for long values in variable length HEX field by @svz-ya in #348
• chore(deps): update golang docker tag to v1.24 by @renovate in #349
• docs: add guide for composite fields by @alovak in #352
• fix(deps): update module golang.org/x/text to v0.23.0 by @renovate in #353
• docs: Explain that subfields can get reordered when packing by @Inuart in #354
• fix a tiny bug by @Viminice in #358
• fix: unmarshaling to []byte for Binary and String fields by @alovak in #364
• fix: resolve G115 integer overflow and exhaustive warnings by @alovak in #365
• feat: add support for anonymous embedded structs in Marshal/Unmarshal by @lsadehaan in #361

New Contributors

• @svz-ya made their first contribution in #348
• @Viminice made their first contribution in #358
• @lsadehaan made their first contribution in #361

Full Changelog: v0.23.2...v0.23.3