chore(release): version packages

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.1.5
+
+### Patch Changes
+
+- f1a3429: The `CLI_PARSER_UNAVAILABLE` message for a missing `@cosyte/fhir` no longer says the package is not on the npm registry: it is. The message now says FHIR support is unavailable in this install, that `@cosyte/fhir` arrives as the peer dependency of `@cosyte/transform` (which an install without peer dependencies, such as npm's `--legacy-peer-deps`, leaves out), and to install `@cosyte/fhir` alongside `@cosyte/cli`. The matching `convert` message no longer makes the same registry claim or says `@cosyte/transform` is missing when only its `@cosyte/fhir` peer is: it names both packages and says to install both alongside `@cosyte/cli`. The code (`CLI_PARSER_UNAVAILABLE`) and exit code (`69`) are unchanged, and both messages stay value-free.
+
 ## 0.1.4
 
 ### Patch Changes

docs-content/installation.md

@@ -85,7 +85,7 @@ autodetector, the exit-code contract, and the value-free diagnostic types:
 ```ts runnable
 import { VERSION } from "@cosyte/cli";
 
-VERSION; // => "0.1.4"
+VERSION; // => "0.1.5"
 ```
 
 If that resolves and prints the release you installed, the install is good: head to the

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cosyte/cli",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "The Cosyte command line for Node.js and TypeScript: one command over HL7 v2, FHIR R4, X12, ASTM, NCPDP, C-CDA, DICOM, and MLLP, with HL7 v2 to FHIR conversion from transform, code mapping from terminology, and the cosyte-mcp MCP server for agents.",
   "keywords": [
     "cli",

src/core/version.ts

@@ -23,4 +23,4 @@
  * console.log(`cosyte ${VERSION}`);
  * ```
  */
-export const VERSION: string = "0.1.4";
+export const VERSION: string = "0.1.5";