[1.x] Publish packages - #1114
Closed
codama-releases[bot] wants to merge 1 commit into
Closed
Conversation
codama-releases
Bot
force-pushed
the
changeset-release/1.x
branch
from
August 27, 2026 14:09
a869cee to
4dd31b5
Compare
codama-releases
Bot
force-pushed
the
changeset-release/1.x
branch
from
August 27, 2026 14:20
4dd31b5 to
1cdab5f
Compare
Closed
Member
|
Closing: after the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 1.x, this PR will be updated.
Releases
@codama/dynamic-address-resolution@1.0.0
Major Changes
b81b87dThanks @lorisleiva! - Promote the package to its first stable major. No API changes are included; this aligns every published package in the monorepo with the 1.x line of the Codama standard ahead of the v2 work.Patch Changes
b4c0206Thanks @plutohan! - Accept bare empty-variant names and indices as enum codec inputs, resolving them to the{ __kind }shape, and match display labels against the discriminated union decoding of scalar enums.b4c0206,abefbeb,b418a9e]:@codama/dynamic-client@1.0.0
Major Changes
b81b87dThanks @lorisleiva! - Promote the package to its first stable major. No API changes are included; this aligns every published package in the monorepo with the 1.x line of the Codama standard ahead of the v2 work.Patch Changes
b4c0206,abefbeb,b4c0206,b418a9e,b81b87d]:@codama/dynamic-instructions@1.0.0
Major Changes
b81b87dThanks @lorisleiva! - Promote the package to its first stable major. No API changes are included; this aligns every published package in the monorepo with the 1.x line of the Codama standard ahead of the v2 work.Patch Changes
b4c0206Thanks @plutohan! - Accept bare empty-variant names and indices as enum codec inputs, resolving them to the{ __kind }shape, and match display labels against the discriminated union decoding of scalar enums.b4c0206,abefbeb,b4c0206,b418a9e,b81b87d]:@codama/fragments@1.0.0
Major Changes
b81b87dThanks @lorisleiva! - Promote the package to its first stable major. No API changes are included; this aligns every published package in the monorepo with the 1.x line of the Codama standard ahead of the v2 work.Patch Changes
abefbeb,b418a9e]:@codama/upgrade@1.0.0
Major Changes
b418a9eThanks @lorisleiva! - Initial release of@codama/upgrade. It upgrades Codama IDLs of any supported major version to the latest major of the standard viaupgrade(rootNode),upgradeFromJson(json), and theupgradeToLatestVisitor()preprocessing visitor (also the package's default export, so"@codama/upgrade"alone works as a CLIbeforevisitor). The frozen v1 node types are exposed under the type-onlyv1namespace. While the latest spec major is 1, upgrading a 1.x IDL is an identity transform plus a restamp to the latest spec version.Patch Changes
fa4a453,abefbeb,55b9ede,dabfe42,b418a9e]:@codama/dynamic-codecs@1.3.0
Minor Changes
#1029
b4c0206Thanks @plutohan! - Breaking: Scalar enums (enums whose variants are all empty) are now encoded and decoded as discriminated unions, consistent with data enums.2{ __kind: 'Down' }2or'down'{ __kind: 'Down' }enumValueNoderesolution2{ __kind: 'Down' }Wire bytes are unchanged; only the JavaScript value shape changes.
Patch Changes
fa4a453,abefbeb,55b9ede,dabfe42,b418a9e]:@codama/errors@1.11.0
Minor Changes
b418a9eThanks @lorisleiva! - Add theCODAMA_ERROR__UNSUPPORTED_VERSIONerror code for Codama IDLs that predate the 1.0.0 specification. TheCODAMA_ERROR__VERSION_MISMATCHmessage now points older versions at the@codama/upgradepackage and newer versions at updating their Codama dependencies.Patch Changes
abefbebThanks @lorisleiva! - FixvalidateCodamaVersionto 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 toCodamaVersionon success, rejects unparsable versions, and no longer special-cases 0.x versions. TheCODAMA_ERROR__VERSION_MISMATCHmessage is reworded accordingly.fa4a453,55b9ede,dabfe42]:@codama/visitors@1.11.0
Minor Changes
362f618Thanks @lorisleiva! - AddcheckCodamaVersionVisitor. It checks the version of the visited Codama IDL against the Codama spec version supported by the installed packages, throwing aCODAMA_ERROR__VERSION_MISMATCHerror when the majors differ. It is mainly useful at IDL-ingestion boundaries that bypasscreateFromRoot, such as abeforevisitor in a Codama CLI config.Patch Changes
fa4a453,abefbeb,55b9ede,dabfe42,b418a9e]:@codama/cli@1.6.3
Patch Changes
fa4a453,362f618,55b9ede,dabfe42]:@codama/dynamic-parsers@1.4.2
Patch Changes
fa4a453,b4c0206,abefbeb,55b9ede,dabfe42,b418a9e]:codama@1.11.0
Patch Changes
abefbebThanks @lorisleiva! - FixvalidateCodamaVersionto 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 toCodamaVersionon success, rejects unparsable versions, and no longer special-cases 0.x versions. TheCODAMA_ERROR__VERSION_MISMATCHmessage is reworded accordingly.fa4a453,abefbeb,362f618,55b9ede,dabfe42,b418a9e]:@codama/node-types@1.11.0
Patch Changes
#1090
fa4a453Thanks @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), theCodamaVersiontype moves from'1.8.0'to'1.9.1', and new documents created viarootNode()are stamped with version1.9.1.#1093
55b9edeThanks @lorisleiva! - Widen theCodamaVersiontype 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 aRootNoderather than only documents carrying the exact pinned version. Add agetCodamaVersionMajor(version)helper to@codama/nodesthat defensively extracts the major from an arbitrary version string, returningnullwhen it cannot be parsed.#1099
dabfe42Thanks @lorisleiva! - Bump the generatedCODAMA_VERSIONto 1.9.2 and refresh the generated documentation from the latest spec.@codama/nodes@1.11.0
Patch Changes
#1090
fa4a453Thanks @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), theCodamaVersiontype moves from'1.8.0'to'1.9.1', and new documents created viarootNode()are stamped with version1.9.1.#1093
55b9edeThanks @lorisleiva! - Widen theCodamaVersiontype 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 aRootNoderather than only documents carrying the exact pinned version. Add agetCodamaVersionMajor(version)helper to@codama/nodesthat defensively extracts the major from an arbitrary version string, returningnullwhen it cannot be parsed.#1099
dabfe42Thanks @lorisleiva! - Bump the generatedCODAMA_VERSIONto 1.9.2 and refresh the generated documentation from the latest spec.Updated dependencies [
fa4a453,abefbeb,55b9ede,dabfe42,b418a9e]:@codama/nodes-from-anchor@1.5.6
Patch Changes
fa4a453,abefbeb,362f618,55b9ede,dabfe42,b418a9e]:@codama/renderers-core@1.4.1
Patch Changes
fa4a453,abefbeb,55b9ede,dabfe42,b418a9e,b81b87d]:@codama/validators@1.11.0
Patch Changes
fa4a453,abefbeb,55b9ede,dabfe42,b418a9e]:@codama/visitors-core@1.11.0
Patch Changes
fa4a453,abefbeb,55b9ede,dabfe42,b418a9e]: