[1.x] Publish packages - #32
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 7, 2026 09:36
11e8bc5 to
5f358ba
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 12:53
5f358ba to
8d51065
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
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/dynamic-instructions@0.4.0
Minor Changes
#1028
a6a9135Thanks @lorisleiva! - Add an offline display dictionary so a renderer (e.g. a hardware wallet) can resolve an instruction's clear-signing display with no network access.DisplayDictionarybundles aDisplayAccountMap(address toEncodedAccount, the offline counterpart of the display layer'sfetchAccount; only existing accounts are stored, so a missing key means "no data") and a genericDisplayNamedMap(address to name — a.soldomain, token symbol, program label, alias…).getRequiredAccountsForDisplaystatically computes which accounts a display would read,getDisplayAccountMapbatch-fetches them via aFetchAccountsFn, andgetDisplayDictionaryCodec(with per-map codecs, each split into…Encoder/…Decoder) serialises the bundle. A filler for the named map is not provided: its data comes from sources Codama has no opinion on.The offline planner and the
whenInjectedskip rule now resolve the provide/inject graph through a single shared walk (resolveInjectionTarget): both follow an injection'sfallbackwhen no provider supplies its key, so a display value reachable only through a fallback is fetched (and hides its member) as it would be at runtime. The walk is cycle-safe, so a self-referential provider resolves to "no value" instead of overflowing the stack.resolveInjectedValue(the display-rendering path) now performs injection selection through the same shared walk, so it too is cycle-safe rather than overflowing on a cyclic provider graph.Patch Changes
#1064
c6a210cThanks @lorisleiva! - Mark unresolved amount scales instead of degrading silently. When anamountNumberDisplayNodeis present but itsdecimalscannot be resolved (e.g. nofetchAccountfor an account-injected scale), the field list now renders the value explicitly marked —1500000 (raw)— and any interpolated sentence referencing it returnsnull, falling back to the field list. Previously the bare integer rendered unmarked in both, reading exactly like a scaled amount. Amount displays authored without adecimalsattribute are unaffected: they remain valid unscaled amounts.#1066
8e89159Thanks @lorisleiva! - Render array values properly in instruction displays. Address arrays expand into one field per element in the fallback list (New Addresses [#1](https://github.com/codama-idl/codama/issues/1),New Addresses [#2](https://github.com/codama-idl/codama/issues/2), …), matching how named and remaining accounts each get their own individually-verifiable line. All other arrays render as a single comma-joined field whose elements go through their item type's presentation (1.5 SOL, 0.5 SOLinstead of a JSON blob), with degraded amount elements marked inline and flagging the whole array. The(raw)marker for unresolved amount scales now lives in the formatted text itself.#1065
75eb574Thanks @lorisleiva! - Render remaining accounts in the fallback display. Trailing account metas now appear in the field list under their group's display label (or a label derived from the group's value name), numbered when a group holds several accounts, and honouring the group'sskipstrategy. When an instruction declares several remaining-accounts groups, each non-final group consumes the run of metas matching itsisSignerflag and the final group takes the rest.#1063
fe893caThanks @lorisleiva! - Match enum variants from every decoded shape when displaying instructions. Scalar enums decoded as numeric discriminators (explicit or positional) now render their variant label instead of the bare index — e.g.Authority Type: Freeze Accountinstead ofAuthority Type: 1— and{ __kind }values match variants regardless of casing.#1062
41282d5Thanks @lorisleiva! - UnwrapOptionvalues when displaying instructions. Display metadata now applies to the value insideoptionTypeNode,zeroableOptionTypeNodeandremainderOptionTypeNodewrappers — e.g. aCOption<u64>lamports amount renders as1.5 SOLinstead of{"__option":"Some","value":"1500000000"}— and absent (None) values render asnone. Flattened option-wrapped structs flatten their inner fields when present and render a singlenonefield when absent.Updated dependencies [
75eb574,d9e7d03,df1792c]:@codama/dynamic-parsers@1.4.0
Minor Changes
#1065
75eb574Thanks @lorisleiva! - Capture trailing account metas on parsed instructions.ParsedInstructiongains an optionalremainingAccountsattribute carrying the concrete metas beyond the instruction's named accounts (e.g. multisig signers), whichparseInstructionnow always populates.#1024
df1792cThanks @plutohan! - Search additional programs when identifying and parsing data.parseInstructionnow uses the instruction'sprogramAddressto restrict the search to the matching program, and identifies nothing when no program of the root matches that address. Allidentify*andparse*functions accept an optionalprogramAddressoption.Patch Changes
#1067
d9e7d03Thanks @lorisleiva! - Returnundefinedinstead of throwing when identified data cannot be decoded. A discriminator can match while the full data does not conform (e.g. truncated or corrupt bytes); theparse*functions now treat that as "not parsable", mirroring theundefinedreturned when nothing is identified.Updated dependencies [
f69845c]:@codama/cli@1.6.1
Patch Changes
f69845c]:@codama/dynamic-address-resolution@0.3.2
Patch Changes
@codama/dynamic-client@0.1.5
Patch Changes
a6a9135,c6a210c,8e89159,75eb574,fe893ca,41282d5]:@codama/dynamic-codecs@1.2.5
Patch Changes
f69845c]:@codama/errors@1.10.1
Patch Changes
@codama/fragments@0.1.4
Patch Changes
#1030
f69845cThanks @ChiefWoods! - fix(nodes): uppercased snake case not correctly converted to snake caseUpdated dependencies []:
codama@1.10.1
Patch Changes
f69845c]:@codama/nodes@1.10.1
Patch Changes
#1030
f69845cThanks @ChiefWoods! - fix(nodes): uppercased snake case not correctly converted to snake caseUpdated dependencies []:
@codama/nodes-from-anchor@1.5.4
Patch Changes
#1030
f69845cThanks @ChiefWoods! - fix(nodes): uppercased snake case not correctly converted to snake caseUpdated dependencies [
f69845c]:@codama/renderers-core@1.3.12
Patch Changes
f69845c]:@codama/validators@1.10.1
Patch Changes
f69845c]:@codama/visitors@1.10.1
Patch Changes
f69845c]:@codama/visitors-core@1.10.1
Patch Changes
f69845c]:@codama/node-types@1.10.1