-
Notifications
You must be signed in to change notification settings - Fork 102
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
Vendor sources of prettyprinter-1.6.0 #1263
Conversation
vendored/prettyprinter-1.6.0/src/Data/Text/Prettyprint/Doc/Render/Terminal.hs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Lars!
|
||
-- servant-0.20 does not yet support aeson-2.2 | ||
-- | ||
constraints: aeson <2.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this change unrelated to the prettyprinter vendoring?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is related because the bound on prettyprinter indirectly implied aeson <2.2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thank you @larskuhtz
Vendor relevant files from prettyerinter-1.6.0. This is a prerequisite for the of mtl-2.3 and latest pact master in chainweb.
As a side effect of the PR, the source-repository-package pin on trifecta can be dropped. It also removes implicit upper bounds on a number of other dependencies like optparse-applicative and configuration tools.
PR checklist:
There are no actual code changes (the code from prettyerinter is copy and pasted without changes, only outdated CPP guarded code is removed) and no behavior changes.
However, due to the implied upgrade of the trifecta version, we have to double check that main net history replay still is not broken, which will be done for the corresponding chainweb-node PR.
Confirm replay/back compat
Mainnet replay succeeded on mtl-2.3 chainweb-node#1709