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

Use multiple top-level values for BuildInfo.purs #1130

Merged
merged 4 commits into from
Dec 4, 2023
Merged

Conversation

JordanMartinez
Copy link
Contributor

Description of the change

Somewhat dependent on #1126 (adds tests). Fixes #1128.

Checklist:

  • Added the change to the "Unreleased" section of the changelog
  • Added some example of the new feature to the README
  • Added a test for the contribution (if applicable)

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 😊

@JordanMartinez
Copy link
Contributor Author

Should these changes be done in #1126?

@f-f
Copy link
Member

f-f commented Dec 3, 2023

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

@JordanMartinez
Copy link
Contributor Author

Helps to push to the right branch...

@JordanMartinez
Copy link
Contributor Author

@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.

@f-f
Copy link
Member

f-f commented Dec 4, 2023

Right - I think the correct procedure is:

  • we merge this
  • I cut a new release
  • then push a commit that re-enables the bootstrap

@JordanMartinez please double check this 😄

@JordanMartinez
Copy link
Contributor Author

That sounds correct to me.

@f-f
Copy link
Member

f-f commented Dec 4, 2023

Great, let's go for it

@f-f f-f merged commit 954f331 into master Dec 4, 2023
3 checks passed
@f-f f-f deleted the jam/update-build-info branch December 4, 2023 17:47
@f-f
Copy link
Member

f-f commented Dec 4, 2023

@f-f
Copy link
Member

f-f commented Dec 6, 2023

@f-f
Copy link
Member

f-f commented Dec 6, 2023

Ah I see - this is because I fixed the output of spago --version to (correctly) go to stdout instead of stderr. Patch incoming

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.

Design of the BuildInfo.purs file
2 participants