Repository navigation
ci(changesets): version packages - #602
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 7, 2026 02:05
9f1370b to
88d6bb8
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 7, 2026 02:36
88d6bb8 to
d954b63
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.
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.19
Patch Changes
9008ebc,b9d1d5e]:@evolution-sdk/evolution@0.5.19
Patch Changes
#603
9008ebcThanks @solidsnakedev! - Decoding then re-encoding a transaction now keeps each inline datum's original bytes, so adding witnesses to a decoded transaction keeps its transaction id. Previously the encoder rewrote an inline datum whose layout differed from the default, for example turning a definite mapa10102intobf0102ff.#599
b9d1d5eThanks @solidsnakedev! -Redeemers.toScriptDataHashnow encodes datums with the codec options it is given. Before, it applied the options to the redeemers only and always wrote datums in the default Plutus data encoding. A hash requested withCBOR.CANONICAL_OPTIONSthen did not match a witness set holding canonical datums, and the node rejected the transaction. Calls without options produce the same hashes as before.@evolution-sdk/devnet@3.0.20
Patch Changes
9008ebc,b9d1d5e]:@evolution-sdk/scalus-uplc@2.0.19
Patch Changes
9008ebc,b9d1d5e]: