Conversation
Unisay
force-pushed
the
yura/v3-value-imports
branch
from
September 14, 2026 10:03
aa7bd9d to
7252ed6
Compare
Unisay
marked this pull request as ready for review
September 14, 2026 10:05
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.
AuctionValidatorandAuctionMintingPolicyare V3 scripts, but they readValuethroughPlutusLedgerApi.V1.Value(lovelaceValueOf,valueOf,flattenValue). Both already import everything else fromPlutusLedgerApi.V3, so this moves theValuenames there too.The accessors reached
PlutusLedgerApi.V3in plutus 1.66.0.0 (IntersectMBO/plutus#7839) and this repository is now pinned at 1.69.0.0, so the imports resolve. Rebased onto main after the sources moved undertemplate/.Prompted by a review comment from @zliu41 on IntersectMBO/plutus#7839.