-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat: migrate to spago@next #27
base: main
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,1170 @@ | |||
{ |
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.
I cloned this PR branch and ran spago build
and it created a completely different spago.lock
file. I wonder why? I'm on spago v0.93.37.
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.
The spago.lock
file is only for development of this package anyway, is my understanding...
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.
$ rm -fdr output && spago build --censor-stats --strict --ensure-ranges --pedantic-packages
no changes
~/projects/contrib/purescript-uint update-spago-next spago --version
0.93.40
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.
The CI passed with spago v0.93.40 https://github.com/purescript-contrib/purescript-uint/actions/runs/11305240509/job/31444528947
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.
Ok I see now that the spago.lock
file format has changed to JSON for spago v0.93.40...
990f4cf
to
cfc1abb
Compare
Description of the change
Clearly and concisely describe the purpose of the pull request. If this PR relates to an existing issue or change proposal, please link to it. Include any other background context that would help reviewers understand the motivation for this PR.
Checklist: