[github-actions]

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

• Updated dependencies [7a25bcd, 36dd2e4]:
  • @evolution-sdk/evolution@0.8.1

@evolution-sdk/evolution@0.8.1

Patch Changes

• #710 7a25bcd Thanks @jorbuedo! - Assets.getByUnit reads a dotted unit (policyId.assetName), which Assets.fromUnit has always accepted. The two disagreed: a value built from a dotted unit answered 0n when read back with that same string, because the reader sliced the dotted text at 56 characters. 0n reads as "this asset is not here", so the disagreement was silent. fromUnit, fromRecord and getByUnit now 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.fromHex accepts either case, so fromUnit built an asset from an uppercase unit that getByUnit then answered 0n for, because it compares against PolicyId.toHex, which emits lowercase. getUnits still emits the canonical lowercase spelling.

  ⚠️ Assets.fromUnit accepts one input it rejected before: the concatenated spelling policyId followed by assetName with no dot, which is what getUnits emits. 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 a PolicyId parse error.

• #709 36dd2e4 Thanks @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.

@evolution-sdk/devnet@3.0.25

Patch Changes

• Updated dependencies [7a25bcd, 36dd2e4]:
  • @evolution-sdk/evolution@0.8.1
  • @evolution-sdk/aiken-uplc@2.0.24
  • @evolution-sdk/scalus-uplc@2.0.24

@evolution-sdk/scalus-uplc@2.0.24

Patch Changes

• Updated dependencies [7a25bcd, 36dd2e4]:
  • @evolution-sdk/evolution@0.8.1