Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bump cardano-ledger-shelley-test minor version #3414

Merged
merged 1 commit into from
May 10, 2023

Conversation

JaredCorduan
Copy link
Contributor

@JaredCorduan JaredCorduan commented May 10, 2023

Description

In a previous PR, the dependency on cardano-ledger-shelley was changes from ^> 1.1 to ^> 1.2 in cardano-ledger-shelley-test, but the version in cardano-ledger-shelley-test was not increased.

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated
  • When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
    versioning process.
  • The version bounds in .cabal files for all affected packages are updated (See RELEASING.md)
  • Any changes are noted in the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
  • Code is formatted with fourmolu (use scripts/fourmolize.sh)
  • Cabal files are formatted (use scripts/cabal-format.sh)
  • hie.yaml has been updated (use scripts/gen-hie.sh)
  • Self-reviewed the diff

In a previous PR, the dependency on cardano-ledger-shelley was
changes from ^> 1.1 to ^> 1.2, but the version in
cardano-ledger-shelley-test was not increased.
@JaredCorduan JaredCorduan requested a review from lehins May 10, 2023 16:33
@JaredCorduan JaredCorduan merged commit b97a91e into master May 10, 2023
@iohk-bors iohk-bors bot deleted the jc/bump_shelly_test_version branch May 10, 2023 17:12
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.

2 participants