Fix issue #11: Use haskell-actions/setup instead of haskell/action/setup#14
Draft
zchn wants to merge 1 commit into
Draft
Fix issue #11: Use haskell-actions/setup instead of haskell/action/setup#14zchn wants to merge 1 commit into
zchn wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request fixes #11.
The issue has been successfully resolved based on the following changes and their impact:
The GitHub Actions workflow files (.github/workflows/examples-test.yml and stack-build.yml) have been updated to replace
haskell/actions/setupwithhaskell-actions/setup@v2, which directly addresses the deprecation warning.The stack.yaml configuration has been significantly updated to support the build with newer package versions:
These changes comprehensively address both requirements:
The changes are focused on configuration updates rather than source code modifications, which was the preferred approach specified in the issue description. The presence of the lock file also indicates that the dependencies have been successfully resolved.
Automatic fix generated by OpenHands 🙌