-
Notifications
You must be signed in to change notification settings - Fork 131
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
Use multiple top-level values for BuildInfo.purs #1130
Conversation
Should these changes be done in #1126? |
Oh, I saw this comment too late - that was a good option, but a new PR works too |
6c6567b
to
bb5aee0
Compare
Helps to push to the right branch... |
@f-f Looks like we got a chicken-and-egg problem. I need to reference the new BuildInfo file to get the bootstrap build step to work, but doing so fails to build the initial code to run the tests. |
This reverts commit 41b8079.
Right - I think the correct procedure is:
@JordanMartinez please double check this 😄 |
That sounds correct to me. |
Great, let's go for it |
Tests fail though: https://github.com/purescript/spago/actions/runs/7090846490/job/19298707004 |
Ah I see - this is because I fixed the output of |
Description of the change
Somewhat dependent on #1126 (adds tests). Fixes #1128.
Checklist:
README
P.S.: the above checks are not compulsory to get a change merged, so you may skip them. However, taking care of them will result in less work for the maintainers and will be much appreciated 😊