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
purescript 0.9.2 #2905
purescript 0.9.2 #2905
Conversation
Any idea why this broke on the CI server, commit seems OK as I would have thought to commit it (sha matches). |
Probably due to a new version of one of deps. |
@schrepfler It's a regression introduced by purescript/purescript@8063c4d This fixes it:
|
So what's the plan, commit upstream and wait for new tag? |
@schrepfler no, I've opened an upstream PR and will apply it as a patch to this PR in the next few minutes: purescript/purescript#2225 |
df8b39f
to
48b6aad
Compare
@DomT4 PR refreshed. @schrepfler you can try it locally if you do |
@ilovezfs 👍 when you're happy. LGTM. Thanks for filing a PR upstream as well! |
Are we merging it then? |
@schrepfler sure. The issues being discussed with upstream regarding the PR are about bumping their Stack requirements which has no effect over here so I'll just refresh this once that's set in stone, hopefully with a new tag too. |
restrict protolude to 0.1.5 to avoid "ambiguous occurrence" errors
48b6aad
to
2f72e9d
Compare
@schrepfler 🚢'd |
Woo hoo upstream PR just merged! purescript/purescript@15c466f |
needed to patch ambiguous occurrence errors