v0.0.13

What changed

• Repository tooling: the PHI scanner now refuses a run that read only some of the targets it enumerated.

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/terminology@0.0.13

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.13

v0.0.12

What changed

Internal tooling and CI only. No change to the published package surface.

Install

npm install @cosyte/terminology@0.0.12

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.12

v0.0.11

What changed

• CHANGELOG.md is now written by the release rather than by hand, so the copy inside every published tarball stops presenting already-shipped work as unreleased.
• The README lockup now links to cosyte.com (ASSETS).

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/terminology@0.0.11

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.11

v0.0.10

What changed

• The publish gate's --no-definitely-typed forwarding was pinned by nothing, so a gate that accepted the flag and then dropped it looked exactly like one that forwards it.

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/terminology@0.0.10

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.10

v0.0.9

What changed

• The publish gate's argument guard refused a fixed list of blinding spellings, and -fjson was not on it: a value fused to a short flag hid the one sentence the gate reads, and it handed back a pass over a tarball carrying no types.
• A symbolic link under a scan root read clean on both of the PHI scanner's enumerating routes, so a link pointing at a file full of real identifiers passed the gate twice over.
• The test suite no longer sets a global timeout, and its one repeated start-up tax is gone: the PHI-scanner sweep was paying a tsx cold start at twenty separate call sites, and spawning node instead roughly halved that file.

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/terminology@0.0.9

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.9

v0.0.8

What changed

• A loaded GEM map, complex map and drug graph froze their wrapper but handed out plain Maps inside it, so a holder could delete a mapping, forge one, or empty a medication's ingredient edges.

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/terminology@0.0.8

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.8

v0.0.7

What changed

• The UCUM unit table loadUcumEssence() hands out was readonly to TypeScript only, so a definition could be rewritten in place, fabricating a unit equivalence that outlived restoring the table.

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/terminology@0.0.7

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.7

v0.0.6

What changed

• A UnitNode you assembled yourself could change how reduce and ucumEqual answer for a unit parsed out of the bundled UCUM table, for the rest of the process.
• Diagnostic and error messages no longer echo a column name, a map direction, a canonical URI, or a unit atom you supplied.

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/terminology@0.0.6

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.6

v0.0.5

What changed

• The README now opens with the Cosyte mark, which follows the reader's color scheme.

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/terminology@0.0.5

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.5

v0.0.4

What changed

• The licence file now says what the package actually distributes: MIT for Cosyte's own code, plus a third-party notices section naming the bundled UCUM table, its copyright and its terms.
• Three published documentation pages carried a link form that MDX cannot compile, which stopped docs.cosyte.com building for every package (TERMINOLOGY-MDX-AUTOLINK). The bare-autolink form is replaced with an explicit link. No engine behaviour, API surface or bundled data changed.

This release carries 0.0.3's content as well as its own. The 0.0.3 version commit was made but never published: a leftover changeset meant that release run only opened the next version PR. The MDX fix above is what 0.0.3 would have carried. 0.0.3 is deliberately not being published after the fact, because npm would order it after 0.0.4.

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/terminology@0.0.4

npm: https://www.npmjs.com/package/@cosyte/terminology/v/0.0.4