[1.x] Publish packages

[codama-releases]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@codama/cli@1.6.3

Patch Changes

• Updated dependencies [fa4a453, 55b9ede]:
  • @codama/nodes@1.10.3
  • @codama/visitors@1.10.3
  • @codama/visitors-core@1.10.3

@codama/dynamic-address-resolution@0.3.4

Patch Changes

• Updated dependencies [abefbeb]:
  • codama@1.10.3
  • @codama/errors@1.10.3
  • @codama/dynamic-codecs@1.2.7

@codama/dynamic-client@0.1.7

Patch Changes

• Updated dependencies [abefbeb]:
  • codama@1.10.3
  • @codama/errors@1.10.3
  • @codama/dynamic-codecs@1.2.7
  • @codama/dynamic-address-resolution@0.3.4
  • @codama/dynamic-instructions@0.4.2

@codama/dynamic-codecs@1.2.7

Patch Changes

• Updated dependencies [fa4a453, abefbeb, 55b9ede]:
  • @codama/nodes@1.10.3
  • @codama/errors@1.10.3
  • @codama/visitors-core@1.10.3

@codama/dynamic-instructions@0.4.2

Patch Changes

• Updated dependencies [abefbeb]:
  • codama@1.10.3
  • @codama/errors@1.10.3
  • @codama/dynamic-codecs@1.2.7
  • @codama/dynamic-parsers@1.4.2
  • @codama/dynamic-address-resolution@0.3.4

@codama/dynamic-parsers@1.4.2

Patch Changes

• Updated dependencies [fa4a453, abefbeb, 55b9ede]:
  • @codama/nodes@1.10.3
  • @codama/errors@1.10.3
  • @codama/dynamic-codecs@1.2.7
  • @codama/visitors-core@1.10.3

@codama/errors@1.10.3

Patch Changes

• #1094 abefbeb Thanks @lorisleiva! - Fix validateCodamaVersion to compare the document's version against the Codama spec version (CODAMA_VERSION) instead of the npm package version, which is an unrelated namespace and caused false mismatches whenever the two drifted apart. The function now accepts any string and narrows it to CodamaVersion on success, rejects unparsable versions, and no longer special-cases 0.x versions. The CODAMA_ERROR__VERSION_MISMATCH message is reworded accordingly.
• Updated dependencies [fa4a453, 55b9ede]:
  • @codama/node-types@1.10.3

@codama/fragments@0.1.6

Patch Changes

• Updated dependencies [abefbeb]:
  • @codama/errors@1.10.3

codama@1.10.3

Patch Changes

• #1094 abefbeb Thanks @lorisleiva! - Fix validateCodamaVersion to compare the document's version against the Codama spec version (CODAMA_VERSION) instead of the npm package version, which is an unrelated namespace and caused false mismatches whenever the two drifted apart. The function now accepts any string and narrows it to CodamaVersion on success, rejects unparsable versions, and no longer special-cases 0.x versions. The CODAMA_ERROR__VERSION_MISMATCH message is reworded accordingly.
• Updated dependencies [fa4a453, abefbeb, 55b9ede]:
  • @codama/nodes@1.10.3
  • @codama/errors@1.10.3
  • @codama/cli@1.6.3
  • @codama/validators@1.10.3
  • @codama/visitors@1.10.3

@codama/node-types@1.10.3

Patch Changes

• #1090 fa4a453 Thanks @lorisleiva! - Update the generated node types and constructors to @codama/spec@1.9.1. Generated docblocks now carry the enriched spec documentation (strategy walkthroughs with buffer diagrams for the offset type nodes, serialisation caveats, and worked examples), the CodamaVersion type moves from '1.8.0' to '1.9.1', and new documents created via rootNode() are stamped with version 1.9.1.

• #1093 55b9ede Thanks @lorisleiva! - Widen the CodamaVersion type from the exact pinned literal ('1.9.1') to a major-pinned template literal (1.${number}.${number}), so any document of the current spec major type-checks as a RootNode rather than only documents carrying the exact pinned version. Add a getCodamaVersionMajor(version) helper to @codama/nodes that defensively extracts the major from an arbitrary version string, returning null when it cannot be parsed.

@codama/nodes@1.10.3

Patch Changes

• #1090 fa4a453 Thanks @lorisleiva! - Update the generated node types and constructors to @codama/spec@1.9.1. Generated docblocks now carry the enriched spec documentation (strategy walkthroughs with buffer diagrams for the offset type nodes, serialisation caveats, and worked examples), the CodamaVersion type moves from '1.8.0' to '1.9.1', and new documents created via rootNode() are stamped with version 1.9.1.

• #1093 55b9ede Thanks @lorisleiva! - Widen the CodamaVersion type from the exact pinned literal ('1.9.1') to a major-pinned template literal (1.${number}.${number}), so any document of the current spec major type-checks as a RootNode rather than only documents carrying the exact pinned version. Add a getCodamaVersionMajor(version) helper to @codama/nodes that defensively extracts the major from an arbitrary version string, returning null when it cannot be parsed.

• Updated dependencies [fa4a453, abefbeb, 55b9ede]:

  • @codama/node-types@1.10.3
  • @codama/errors@1.10.3

@codama/nodes-from-anchor@1.5.6

Patch Changes

• Updated dependencies [fa4a453, abefbeb, 55b9ede]:
  • @codama/nodes@1.10.3
  • @codama/errors@1.10.3
  • @codama/visitors@1.10.3

@codama/renderers-core@1.4.1

Patch Changes

• Updated dependencies [fa4a453, abefbeb, 55b9ede]:
  • @codama/nodes@1.10.3
  • @codama/errors@1.10.3
  • @codama/visitors-core@1.10.3
  • @codama/fragments@0.1.6

@codama/validators@1.10.3

Patch Changes

• Updated dependencies [fa4a453, abefbeb, 55b9ede]:
  • @codama/nodes@1.10.3
  • @codama/errors@1.10.3
  • @codama/visitors-core@1.10.3

@codama/visitors@1.10.3

Patch Changes

• Updated dependencies [fa4a453, abefbeb, 55b9ede]:
  • @codama/nodes@1.10.3
  • @codama/errors@1.10.3
  • @codama/visitors-core@1.10.3

@codama/visitors-core@1.10.3

Patch Changes

• Updated dependencies [fa4a453, abefbeb, 55b9ede]:
  • @codama/nodes@1.10.3
  • @codama/errors@1.10.3