Skip to content

Conversation

@bezirg
Copy link
Collaborator

@bezirg bezirg commented Dec 3, 2025

Description

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.

@bezirg bezirg requested a review from a team as a code owner December 3, 2025 13:10
Copy link
Collaborator

@lehins lehins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Beside the comment about the lower bound we also need to update index-state for CHaP and nix flake in order to bring in the new version of plutus


transBoundedRational :: BoundedRational r => r -> PV3.Rational
transBoundedRational = PV3.fromGHC . unboundRational
transBoundedRational = PV3.fromHaskellRatio . unboundRational
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bezirg, which version of plutus-ledger-api started exporting fromHaskellRatio? We need to add a lower bound in the cabal file on that version in order to make sure cabal doesn't try to build an incompatible version.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be plutus 1.56.0.0 which is not released yet. @Unisay is on it to release it with the way you proposed in ChaP

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.

3 participants