Skip to content

Update to Plinth 1.72 (9.12) - #9

Open
hsyl20 wants to merge 1 commit into
ghc-9.12from
plutus-1.72-9.12
Open

hsyl20 wants to merge 1 commit into
ghc-9.12from
plutus-1.72-9.12

Conversation

@hsyl20

@hsyl20 hsyl20 commented Nov 17, 2026

Copy link
Copy Markdown
Collaborator

Bump the plutus submodule to Plinth 1.72 (fork branch plinthc-1.72, the plinthc patches rebased on 1.72.0.0), the GHC fork to version 9.12.172, and the plutus-* bounds of the test project.

Upstream changes that matter here:

  • 1.71 makes Plutus Core 1.2.0 the default target version, which the ledger permits from protocol version 12 only; 1.72 makes the case on Data depend on it. The fork option target-protocol-version (default 11, mainnet) now caps the Plutus Core version at 1.1.0 below protocol version 12, so a default build still runs on mainnet.
  • liftCodeDef now gives a 1.2.0 program, so validator unsafeApplyCode liftCodeDef params failed on the version check for mainnet code. The fork makes applyCode give the argument the version of the function.
  • The ledger-API test of a PV12 script at PV11 now expects the rejection of Plutus Core 1.2.0 at deserialisation, and the PV11 dataFields golden takes the upstream 1.1.0 encoding (a case on the unConstrData pair).

Locally, the GHC 9.12 build passes every suite except that golden, regenerated here; the GHC 9.6 run was not completed locally.

🤖 Generated with Claude Code

- plutus: branch plinthc-1.72 of the fork (the Plinth patches on top of
  1.72.0.0). Since 1.71 the default Plutus Core version is 1.2.0, which
  the ledger permits from protocol version 12 only, so target-protocol-
  version (default 11) now caps it at 1.1.0, and applyCode gives the
  argument the version of the function so that liftCodeDef still applies
  to code compiled for mainnet.
- ghc: version 9.12.172 (plinthc-9.12.4).
- plinth/test: plutus-* ^>=1.72.0.0.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant