Updates to stack.yaml and stack.yaml.lock #388
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
Ouch. And it worked fine in my AppVeyor |
- Upgrading to Stack v2.1.3 from v1.9.3 on Windows, time-1.8.0.4 was required in stack.yaml - This in turn caused unix-2.7.2.2 to be required for the MacOS build - Upgraded Stack in the Appveyor script to v2.1.1 (the chocolatey package for 2.1.3 is currently broken) - Also updated the stack.yaml.lock file (modifying commit message to trigger new build)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On upgrading to Stack v2.1.3 from v1.9.3 on Windows,
time-1.8.0.4wasrequired in stack.yaml
unix-2.7.2.2to be required for the MacOS buildpackage for 2.1.3 is currently broken)