update ledger and plutus #4059
Merged
update ledger and plutus #4059
Conversation
This file contains 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
The update to ledger brings two small but nice improvements: * the SuccessfulPlutusScriptsEvent doesn't fire on an empty list anymore * we do not serialize empty txbody fields anymore The update to plutus removes the V2 size limit
JaredCorduan
requested review from
dcoutts,
Jimbo4350,
erikd and
newhoggy
as code owners
9 tasks
Jimbo4350
approved these changes
Jun 16, 2022
|
bors merge |
|
Build succeeded: |
10 tasks
iohk-bors bot
added a commit
to IntersectMBO/ouroboros-network
that referenced
this pull request
Jun 17, 2022
3812: update ledger and plutus r=JaredCorduan a=JaredCorduan The update to ledger brings two small but nice improvements: * the `SuccessfulPlutusScriptsEvent` doesn't fire on an empty list anymore * we do not serialize empty txbody fields anymore The update to plutus removes the V2 size limit These two updates match the updates in this node PR: IntersectMBO/cardano-node#4059 # Checklist - Branch - [x] Commit sequence broadly makes sense - [x] Commits have useful messages - [ ] New tests are added if needed and existing tests are updated - [ ] If this branch changes Consensus and has any consequences for downstream repositories or end users, said changes must be documented in [`interface-CHANGELOG.md`](../ouroboros-consensus/docs/interface-CHANGELOG.md) - [ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in [`interface-CHANGELOG.md`](../docs/interface-CHANGELOG.md) - [ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional. - Pull Request - [ ] Self-reviewed the diff - [ ] Useful pull request description at least containing the following information: - What does this PR change? - Why these changes were needed? - How does this affect downstream repositories and/or end-users? - Which ticket does this PR close (if any)? If it does, is it [linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)? - [x] Reviewer requested Co-authored-by: Jared Corduan <jaredcorduan@gmail.com>
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.
The update to ledger brings two small but nice improvements:
SuccessfulPlutusScriptsEventevent doesn't fire on an empty list anymoreThe update to Plutus removes the V2 size limit