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

Backport mint field translation bugfix #3567

Conversation

lehins
Copy link
Contributor

@lehins lehins commented Jul 21, 2023

Description

This is a backport fix of #3566

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. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
  • All visible changes are prepended to 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

@lehins lehins force-pushed the release/mint-field-translation-bugfix branch from bb4b3d0 to 6611db4 Compare July 21, 2023 21:45
@lehins lehins changed the title Release/mint field translation bugfix Backport mint field translation bugfix Jul 21, 2023
@lehins lehins merged commit 62ed994 into release/ref-inputs-witnessing-bug-fix Jul 24, 2023
20 of 44 checks passed
@iohk-bors iohk-bors bot deleted the release/mint-field-translation-bugfix branch July 24, 2023 12:02
@lehins lehins restored the release/mint-field-translation-bugfix branch July 24, 2023 20:40
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.

None yet

1 participant