Repository navigation
ci(changesets): version packages - #728
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
November 13, 2026 07:51
595cbc6 to
ae4b652
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 13, 2026 08:07
ae4b652 to
a23c222
Compare
This branch has not been deployed
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
@evolution-sdk/aiken-uplc@2.0.24
Patch Changes
7a25bcd,36dd2e4,cd2d9b3,1d9c06a]:@evolution-sdk/evolution@0.8.1
Patch Changes
#710
7a25bcdThanks @jorbuedo! -Assets.getByUnitreads a dotted unit (policyId.assetName), whichAssets.fromUnithas always accepted. The two disagreed: a value built from a dotted unit answered0nwhen read back with that same string, because the reader sliced the dotted text at 56 characters.0nreads as "this asset is not here", so the disagreement was silent.fromUnit,fromRecordandgetByUnitnow share one parse, and a dot cannot occur in hex, so both spellings stay unambiguous.The same shared parse reads a unit case-insensitively.
Bytes.fromHexaccepts either case, sofromUnitbuilt an asset from an uppercase unit thatgetByUnitthen answered0nfor, because it compares againstPolicyId.toHex, which emits lowercase.getUnitsstill emits the canonical lowercase spelling.Assets.fromUnitaccepts one input it rejected before: the concatenated spellingpolicyIdfollowed byassetNamewith no dot, which is whatgetUnitsemits. Sharing the parse means a dotless unit longer than 56 characters now splits at 56, where before the whole string was taken as the policy id and failed with aPolicyIdparse error.#709
36dd2e4Thanks @jorbuedo! - Decoding a transaction body refuses a key the schema does not model, instead of dropping it. The decoder reads its fields by key, so a key it never reads is absent from the result and missing from the re-encode: measured on a mainnet transaction, a body given one extra key went in at 1271 bytes and came back out as the original 1268, byte for byte, with nothing raised, as a different transaction with a different id. Every valid Conway body key is modelled, so an unmodelled key is either a pre-Conway field this schema cannot represent or a field from a newer era, and carrying the bytes through would let a wallet sign a field it cannot display.#711
cd2d9b3Thanks @jorbuedo! -NativeScripts.toJSONrefuses aslotorrequiredoutside ±Number.MAX_SAFE_INTEGERinstead of truncating it. The cardano-cli JSON form carries both as JSON numbers, so auint64slot above 2^53-1 has no exact representation in it, andNumber(slot)returned a different slot with no error;requiredis anint64the ledger allows to be negative, so the lower bound is reachable the same way. A script decoded from the chain may carry either, so this was reachable on read, not only when authoring a script. The refusal is the module'sNativeScriptError, so callers can catch it by tag.NativeScript'sHash.symbolnow hashes the variant structurally instead of routing throughtoJSON, so such a script still hashes and compares. The structural hash also hashes a key hash from its bytes rather than its container, which keepsEqual.equalstrue for aBufferand aUint8Arrayover the same bytes.#712
1d9c06aThanks @jorbuedo! -TransactionOutputis deprecated in favour ofTxOut. It is a second, parallel model of a transaction output (address: AddressEras,amount: Value, a Shelley and a Babbage class) whileTxOutcarries the oneTransactionBody, the builders and the sdk use (address: Address,assets: Assets, one class for both eras). Both are public under names that give no hint which is which, and they reject each other: an output built withTransactionOutputcannot go into aTransactionBody. Nothing is removed or re-pointed, so no caller breaks.Every export of the module carries the tag, each naming its
TxOutcounterpart, since TypeScript cannot deprecate a namespace re-export and a tag on the module alone reaches no caller.@evolution-sdk/devnet@3.0.25
Patch Changes
7a25bcd,36dd2e4,cd2d9b3,1d9c06a]:@evolution-sdk/scalus-uplc@2.0.24
Patch Changes
7a25bcd,36dd2e4,cd2d9b3,1d9c06a]: