0.2.0 - 2022-09-09
This is a minor release for the Slither Action - the Github Action for Slither.
This release introduces two main features:
New fail-on option.
This option lets you configure the action step to only fail if findings of a certain severity are found. For example, fail-on: medium would only cause the action to fail if medium or high severity findings are detected. Refer to the corresponding section in the README for more details. This feature requires using Slither 0.9.0 or later for the best effect.
If you are using the action with the SARIF integration, note that you may now use fail-on: none instead of having to continue-on-error: true. This will result in an overall more robust setup, which will not mask build or other such failures. Refer to the updated examples in the README for the recommended way to use fail-on in this case.
Updated slither-version option.
This option has been extended, and it can now also accept Git references as well as PyPI release numbers. You can learn more about this change in the README document.
What's Changed
- Foundry support - now foundry will be installed in the container if a target requires it to be built
- Enhanced compatibility with manually built projects, and projects with special compilation arguments
- Improved solc version detection for glob targets
- pnpm support for dependency management
slither-versioncan now also accept git refs- New
fail-onoption, to specify when should the action fail. When combined with Slither 0.9.0, you can now choose to fail the action step if issues of a certain severity are found.
New Contributors
Thanks to the new contributors in this release!
- @OliverNChalk made their first contribution in #12
- @0xCLARITY made their first contribution in #27
- @vzctl made their first contribution in #26
Full Changelog: v0.1.1...v0.2.0
