Skip to content

Move Arbitrary instances to cardano-base#5553

Draft
neilmayhew wants to merge 11 commits intomasterfrom
nm/cardano-base-orphans
Draft

Move Arbitrary instances to cardano-base#5553
neilmayhew wants to merge 11 commits intomasterfrom
nm/cardano-base-orphans

Conversation

@neilmayhew
Copy link
Contributor

Description

We have Arbitrary instances for various cardano-base types. These need to be moved to the corresponding testlibs in cardano-base so that we can improve our cardano-base tests.

Checklist

  • Commits in meaningful sequence and with useful messages.
  • Tests added or updated when needed.
  • CHANGELOG.md files updated for packages with externally visible changes.
    NOTE: New section is never added with the code changes. (See RELEASING.md).
  • Versions updated in .cabal and CHANGELOG.md files when necessary, according to the
    versioning process.
  • Version bounds in .cabal files updated when necessary.
    NOTE: If bounds change in a cabal file, that package itself must have a version increase. (See RELEASING.md).
  • Code formatted (use scripts/fourmolize.sh).
  • Cabal files formatted (use scripts/cabal-format.sh).
  • CDDL files are up to date (use scripts/gen-cddl.sh)
  • hie.yaml updated (use scripts/gen-hie.sh).
  • Self-reviewed the diff.

This brings in the revised upper bounds in cardano-ledger-tests
This previews what will eventually be released to CHaP and this commit
should be dropped after new cardano-base packages are released
The `allow-newer: plutus-core:cardano-crypto-class` in `cabal.project`
should be dropped when a suitable release of `plutus-core` is available
@neilmayhew neilmayhew force-pushed the nm/cardano-base-orphans branch from 1fd47f0 to 566b9b7 Compare February 2, 2026 22:49
@neilmayhew neilmayhew force-pushed the nm/cardano-base-orphans branch from 566b9b7 to e30bad8 Compare February 3, 2026 00:14
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