Bump @codama/spec to 1.6.0-rc.6#1001
Merged
Merged
Conversation
Member
Author
This was referenced May 21, 2026
lorisleiva
force-pushed
the
05-14-generate_codama_visitors-core_s_identityvisitor_and_mergevisitor_from_codama_spec_
branch
from
1d45ad2 to
70df4fa
Compare
lorisleiva
force-pushed
the
05-20-bump_codama_spec_to_1.6.0-rc.6
branch
from
9319068 to
28694e1
Compare
🦋 Changeset detectedLatest commit: 2cc8290 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
🦋 Changeset detectedLatest commit: 28694e1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
lorisleiva
force-pushed
the
05-14-generate_codama_visitors-core_s_identityvisitor_and_mergevisitor_from_codama_spec_
branch
from
70df4fa to
d197456
Compare
lorisleiva
force-pushed
the
05-20-bump_codama_spec_to_1.6.0-rc.6
branch
from
28694e1 to
00d7045
Compare
lorisleiva
force-pushed
the
05-14-generate_codama_visitors-core_s_identityvisitor_and_mergevisitor_from_codama_spec_
branch
from
d197456 to
82a8a16
Compare
lorisleiva
force-pushed
the
05-20-bump_codama_spec_to_1.6.0-rc.6
branch
2 times, most recently
from
00c09c7 to
66505b0
Compare
lorisleiva
force-pushed
the
05-14-generate_codama_visitors-core_s_identityvisitor_and_mergevisitor_from_codama_spec_
branch
2 times, most recently
from
03e7196 to
e9a89fe
Compare
lorisleiva
force-pushed
the
05-20-bump_codama_spec_to_1.6.0-rc.6
branch
from
66505b0 to
be79b8b
Compare
Base automatically changed from
05-14-generate_codama_visitors-core_s_identityvisitor_and_mergevisitor_from_codama_spec_
to
main
June 11, 2026 10:54
Pulls in the camelCase rename of every spec union and enumeration name, the new `{ kind: 'address' }` `TypeExpr` (rendered as plain `string` on the v1 TS surface), and the rc.6 revert of the rc.5 vec-of-children optional flips — leaving `programNode`, `rootNode`, `instructionNode`, `pdaNode`, and `pdaValueNode`'s child arrays required as they were in rc.4. The generator picks up the new `address` kind in both `nodeTypes` and `nodes` `typeExpr` fragments, switches the `registered*` prefix and `UNION_ALIAS_NAMES` keys to camelCase to match the new spec naming, and gains a small constructor-signature fix to avoid emitting invalid `param?: T = default` TypeScript whenever an attribute that's both optional and supplied with a default appears (no such attribute exists in v1 today, but the bug would have surfaced the moment one did). The regenerated `@codama/node-types` surface differs from rc.4 by a single docstring paragraph on `NestedTypeNode` — the spec's nested-union alias name is now camelCase. Test fixtures across the generator's suite are updated to mirror the new convention; runtime behaviour and the public TS API are unchanged.
lorisleiva
force-pushed
the
05-20-bump_codama_spec_to_1.6.0-rc.6
branch
from
be79b8b to
2cc8290
Compare
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.
Pulls in the camelCase rename of every spec union and enumeration name, the new
{ kind: 'address' }TypeExpr(rendered as plainstringon the v1 TS surface), and the rc.6 revert of the rc.5 vec-of-children optional flips — leavingprogramNode,rootNode,instructionNode,pdaNode, andpdaValueNode's child arrays required as they were in rc.4. The generator picks up the newaddresskind in bothnodeTypesandnodestypeExprfragments, switches theregistered*prefix andUNION_ALIAS_NAMESkeys to camelCase to match the new spec naming, and gains a small constructor-signature fix to avoid emitting invalidparam?: T = defaultTypeScript whenever an attribute that's both optional and supplied with a default appears (no such attribute exists in v1 today, but the bug would have surfaced the moment one did). The regenerated@codama/node-typessurface differs from rc.4 by a single docstring paragraph onNestedTypeNode— the spec's nested-union alias name is now camelCase. Test fixtures across the generator's suite are updated to mirror the new convention; runtime behaviour and the public TS API are unchanged.