v14.52.1

v14.52.1 - 2026-08-28

• 🚀 pathName => fileURLToPathname for better windows support

�

v14.52.0

v14.52.0 - 2025-08-11

• 🎉 Add CoTParser.from_xml_document() for parsing multi-event XML documents (ie: the TAK Server Mission API CoT endpoint) - each event is parsed & validated individually and returned in cots, with unparseable events collected in invalid as { error, event } (the raw unmutated xml-js event) so a single poisoned CoT doesn't prevent valid CoTs from being returned
• ✅ from_xml_document coverage: mixed valid/poisoned documents, ordering, bare <event> root, XML declaration, boolean attr normalization, pristine invalid events, Flow-Tag absence & GeoJSON conversion of parsed CoTs

�

v14.51.0

v14.51.0 - 2025-08-05

• 🐛 The SIDC is now emitted on both the __milsym & __milicon details - the takkernel MilSymDetailHandler registers __milsym only, while newer clients read __milicon (ATAK-20119), so MIL-STD symbols previously failed to render depending on the receiving client's version
• 🎉 Add Type2525.cotTypeFromNumericSIDC() - returns the most specific CoT Type a numeric SIDC can express (a-f-G-U-C-I instead of a-f-G), preserving the Type derived icon fallback for clients that can't resolve the SIDC. A numeric SIDC on the GeoJSON type property now uses it
• 🐛 Type2525.to2525D() short codes (types with no Function ID) declared an undefined 12 SIDC Version field, which clients can't map to a symbology provider - they now declare 10 (2525D) like converted codes do

�

v14.50.0

v14.50.0 - 2025-08-01

• 🐛 MilIcon augmentation no longer clobbers an existing __milicon detail with the generic SIDC derived from the CoT type

�

v14.49.0

v14.49.0 - 2025-07-29

• 🎉 Add event Link Attribute for marking a CoT as the projection of a CloudTAK Core Event

�

v14.48.0

v14.48.0 - 2025-07-23

• 🚀 Update normalize function to allow 2525E => type

�

v14.47.0

v14.47.0 - 2025-07-21

• 🎉 Allow a numeric 2525D/2525E SIDC to be provided on the GeoJSON type property - it is mapped to a basic CoT Atom type (a-<affiliation>-<battle dimension>) and the SIDC is placed in the milicon property

�

v14.46.0

v14.46.0 - 2025-07-21

• 🚀 Differentiate between force delete and force stale

�

v14.45.1

v14.45.1 - 2025-07-17

• 🐛 Make uid attributes optional

�

v14.45.0

v14.45.0 - 2025-07-14

• ⬆️ Remove the need for uuid by using crypto.randomUUID() which is available in Node 18+

�