[1.x] Publish packages - #1022
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
July 20, 2026 19:39
0f1bfd6 to
554e210
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 23, 2026 17:26
554e210 to
81622c2
Compare
lorisleiva
approved these changes
Jul 26, 2026
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 main, this PR will be updated.
Releases
@codama/cli@1.6.0
Minor Changes
d3e7f01Thanks @plutohan! - Add anadditionalIdlsconfig option to generate clients for multiple programs in an Anchor workspace from a singlecodama.jsonPatch Changes
add9be2,61ac0a6]:@codama/node-types@1.10.0
Minor Changes
#1025
add9be2Thanks @lorisleiva! - Omit empty array attributes from nodes, and default absent arrays to[]on read.Every node array attribute — whether previously required (e.g.
programNode.accounts,instructionNode.arguments,structTypeNode.fields) or optional (e.g.instructionNode.discriminators) — is now omitted from the node when empty, and defaults to[]when absent. An absent array and an empty array are semantically identical, so this keeps encoded IDLs small (they are often uploaded on-chain) and makes adding or omitting an array attribute non-breaking. Reading remains backwards-compatible: IDLs that still serialise empty arrays continue to parse, and every visitor and accessor normalises an absent array to[].Breaking type change. While runtime reads stay backwards-compatible, this is a breaking change at the type level for external consumers such as renderers and community packages. Array attributes are now typed as optional on the node interfaces (e.g.
ProgramNode.accountsis nowreadonly accounts?: AccountNode[]), so any code that reads an array attribute without guarding — e.g.program.accounts.map(…)— must now coalesce with?? []((program.accounts ?? []).map(…)). Type-parameter constraints also widen fromArray<T>toArray<T> | undefined, so indexing into these types (e.g.InstructionNode['arguments'][number]) must be rewritten asNonNullable<InstructionNode['arguments']>[number]. Consumers should expect compile errors on the first unguarded array read after upgrading and add?? []guards accordingly.@codama/nodes@1.10.0
Minor Changes
#1025
add9be2Thanks @lorisleiva! - Omit empty array attributes from nodes, and default absent arrays to[]on read.Every node array attribute — whether previously required (e.g.
programNode.accounts,instructionNode.arguments,structTypeNode.fields) or optional (e.g.instructionNode.discriminators) — is now omitted from the node when empty, and defaults to[]when absent. An absent array and an empty array are semantically identical, so this keeps encoded IDLs small (they are often uploaded on-chain) and makes adding or omitting an array attribute non-breaking. Reading remains backwards-compatible: IDLs that still serialise empty arrays continue to parse, and every visitor and accessor normalises an absent array to[].Breaking type change. While runtime reads stay backwards-compatible, this is a breaking change at the type level for external consumers such as renderers and community packages. Array attributes are now typed as optional on the node interfaces (e.g.
ProgramNode.accountsis nowreadonly accounts?: AccountNode[]), so any code that reads an array attribute without guarding — e.g.program.accounts.map(…)— must now coalesce with?? []((program.accounts ?? []).map(…)). Type-parameter constraints also widen fromArray<T>toArray<T> | undefined, so indexing into these types (e.g.InstructionNode['arguments'][number]) must be rewritten asNonNullable<InstructionNode['arguments']>[number]. Consumers should expect compile errors on the first unguarded array read after upgrading and add?? []guards accordingly.#1023
61ac0a6Thanks @lorisleiva! - Integrate@codama/spec@1.8.0, adding thepluginNodeto the node meta-model. ApluginNodeattaches named, plugin-specific data to a node: it carries anamethat uniquely identifies the plugin and an optional opaquepayload. The payload is typed by the newjsontype expression, which renders asunknownin TypeScript.instructionNodegains an optionalpluginsfield holding an array ofpluginNode. All changes are additive and optional.Patch Changes
add9be2]:@codama/dynamic-address-resolution@0.3.1
Patch Changes
@codama/dynamic-client@0.1.4
Patch Changes
@codama/dynamic-codecs@1.2.4
Patch Changes
add9be2,61ac0a6]:@codama/dynamic-instructions@0.3.1
Patch Changes
@codama/dynamic-parsers@1.3.1
Patch Changes
add9be2,61ac0a6]:@codama/errors@1.10.0
Patch Changes
add9be2]:@codama/fragments@0.1.3
Patch Changes
codama@1.10.0
Patch Changes
add9be2,62af2ed,61ac0a6,d3e7f01]:@codama/nodes-from-anchor@1.5.3
Patch Changes
add9be2,61ac0a6]:@codama/renderers-core@1.3.11
Patch Changes
add9be2,61ac0a6]:@codama/validators@1.10.0
Patch Changes
#1017
62af2edThanks @cds-amal! - FixgetValidationItemsVisitorthrowingExpected node of kind [definedTypeLinkNode]on any nesteddefinedTypeLinkNode(a struct field, argument, array element, or PDA seed), and recordingValidationItempaths that omitted the node itself. The visitor now composesrecordNodeStackVisitoroutermost, like every other visitor, so the current node is on the stack when validation runs.Updated dependencies [
add9be2,61ac0a6]:@codama/visitors@1.10.0
Patch Changes
add9be2,61ac0a6]:@codama/visitors-core@1.10.0
Patch Changes
add9be2,61ac0a6]: