Skip to content

Conversation

andreasabel
Copy link
Member

The options enable-stack, stack-no-global, stack-setup-ghc and disable-matcher are now proper booleans only accepting true or false. Previously, they were true when set to some non-empty string, even when set to "false" or "off" etc.

disable-matcher is deprecated in favour of a new positive form enable-matcher.

enable-stack is now implied by setting another stack-related option, i.e., one of stack-version, stack-no-global and stack-setup-ghc. Previously, it was a prerequisite to these options.

Contradictory options now give an error, such as stack-no-global with ghc-version or enable-stack: false with stack-version.

Fixes: haskell/actions#142

@andreasabel andreasabel added the re: inputs Concerning inputs and options of the action label May 3, 2023
@andreasabel andreasabel added this to the 3.0.0 milestone May 3, 2023
@andreasabel andreasabel self-assigned this May 3, 2023
The options `enable-stack`, `stack-no-global`, `stack-setup-ghc` and `disable-matcher` are now proper booleans only accepting `true` or `false`.
Previously, they were true when set to some non-empty string, even when set to "false" or "off" etc.

`disable-matcher` is deprecated in favour of a new positive form `enable-matcher`.

`enable-stack` is now implied by setting another stack-related option, i.e., one of `stack-version`, `stack-no-global` and `stack-setup-ghc`.
Previously, it was a prerequisite to these options.

Contradictory options now give an error, such as `stack-no-global` with `ghc-version` or `enable-stack: false` with `stack-version`.

Fixes: haskell/actions#142
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
re: inputs Concerning inputs and options of the action
Projects
None yet
Development

Successfully merging this pull request may close these issues.

enable-stack: true should be implied by other stack-related options
1 participant