@cosyte/terminology 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.1
+
+### Patch Changes
+
+- 6ac6a32: Doc comments in the type declarations no longer use the en dash: the UCUM copyright line reads "©1999-2024", as the published notice does, and a similarity bound reads "`0` to `1`".
+
+  No code system, map, value set, result or diagnostic changes. The README, the documentation and `vendor/ucum/NOTICE.md` get the same edit, matching this package's LICENSE, and the repository's dash check now refuses the en dash in every spelling it already refused the em dash in.
+
 ## 0.1.0
 
 ### Minor Changes
@@ -352,7 +360,7 @@
 
 - 9b5b390: The npm `description` no longer carries an em dash (`EMDASH-CONFORMANCE`).
 
-  The brand rule bans U+2014 on every cosyte surface, and this string is the most visible one the
+  The brand rule bans U+2014 on every Cosyte surface, and this string is the most visible one the
   package has: it is the subtitle on the npm package page and the one line shown in every npm search
   result. It now reads with a colon, which is what the rule's own remedy list names first.
 
@@ -428,7 +436,7 @@ in `0.0.4`. It is not a hole to be filled, because publishing a `0.0.3` now woul
 
 The entries below follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the generated
 sections above use the format Changesets writes, which is a version heading and a list of the
-changes that release consumed. Versions follow the cosyte pre-alpha ladder, `0.0.x` until first
+changes that release consumed. Versions follow the Cosyte pre-alpha ladder, `0.0.x` until first
 alpha, rather than [Semantic Versioning](https://semver.org/spec/v2.0.0.html) alone.
 
 ### Fixed
@@ -1497,7 +1505,7 @@ has_ingredient IN`). RxNorm authors no such relationship in any release: the ing
 
 ## [0.0.1] - 2026-07-21
 
-The first pre-alpha release. The package begins its public history at `0.0.x`, per the cosyte version
+The first pre-alpha release. The package begins its public history at `0.0.x`, per the Cosyte version
 ladder (`0.0.x` until first alpha).
 
 ### Security

package/README.md

@@ -152,7 +152,7 @@ ucumEqual("Cel", "K"); // false: a special (non-linear) unit is never equated wi
 
 The UCUM table is the official `ucum-essence.xml` (version 2.2), and it **is bundled with this
 package**: embedded verbatim in the published build and parsed at runtime. It is copyright
-©1999–2024 Regenstrief Institute, Inc., reproduced under the UCUM Copyright Notice and License
+©1999-2024 Regenstrief Institute, Inc., reproduced under the UCUM Copyright Notice and License
 (<https://ucum.org/license>); the engine ships no derivative of it. It passes the official UCUM
 functional-test cases it claims, and claims no more than it runs: see
 [UCUM conformance](#ucum-conformance). The full notice ships in the package at
@@ -320,7 +320,7 @@ The engine bundles **no code-system release**. What it _does_ bundle includes th
 with its copyright:
 
 - **The UCUM unit table**: `ucum-essence.xml`, version 2.2, revision-date 2024-06-17. The Unified
-  Code for Units of Measure (UCUM) is copyright ©1999–2024 Regenstrief Institute, Inc., all rights
+  Code for Units of Measure (UCUM) is copyright ©1999-2024 Regenstrief Institute, Inc., all rights
   reserved, and is reproduced **verbatim** under the UCUM Copyright Notice and License
   (<https://ucum.org/license>). It is embedded byte-for-byte in the published build and parsed at
   runtime; no modified or derivative copy is distributed. The UCUM Specification is provided "as is"

package/dist/index.cjs

@@ -4979,7 +4979,7 @@ function approximateMatch(graph, query, options = {}) {
 }
 
 // src/index.ts
-var VERSION = "0.1.0";
+var VERSION = "0.1.1";
 
 exports.COMPLEX_MAP_SOURCE_SYSTEM = COMPLEX_MAP_SOURCE_SYSTEM;
 exports.DIAGNOSTIC_CODES = DIAGNOSTIC_CODES;