v0.4.0

0.4.0 - 2024-05-01

This is a minor release for the Slither Action - the Github Action for Slither.

This release introduces one new feature -- support for external Slither plugins.

Plugin support

You can now use the new slither-plugins property to point to a pip requirements file to install alongside Slither. This may be used to install additional third-party or in-house detectors. Refer to the new example in the README for a sample workflow using this new feature.

What's Changed

• Add a way to install Slither plugins by @elopez in #21
• Fix an issue where the stdout property may not be available if Slither has findings.

Full Changelog: v0.3.2...v0.4.0

v0.3.2

0.3.2 - 2024-04-01

This is a patch release for the Slither Action - the Github Action for Slither.

What's Changed

• Add license file by @elopez in #77
• Always create compatibility symlink by @elopez in #76

Full Changelog: v0.3.1...v0.3.2

v0.3.1

0.3.1 - 2024-01-31

This is a patch release for the Slither Action - the Github Action for Slither.

What's Changed

• Create CODEOWNERS by @ggrieco-tob in #54
• Upgrade foundryup version by @elopez in #67
• Improve markdown checklist example in README by @elopez in #62
• Update references to actions in README by @elopez in #68

New Contributors

• @ggrieco-tob made their first contribution in #54

Full Changelog: v0.3.0...v0.3.1

v0.3.0

0.3.0 - 2023-02-21

This is a minor release for the Slither Action - the Github Action for Slither.

This release introduces one new feature. It also fixes an issue with Foundry projects, caused by recent mitigations implemented in git.

New stdout output.

This new output value lets you capture and use the output from Slither. This can be useful, for instance, to produce a Markdown report in combination with the Slither --checklist flag. Refer to the new example in the README for a sample workflow using this new feature.

What's Changed

• Update deprecated set-output clause by @jporzucek in #45
• Add stdout output by @tlvince in #13
• Mark git repositories as safe inside the slither-action container by @elopez in #50
• Enable pipefail by @elopez in #51

New Contributors

Thanks to the new contributors in this release!

• @jporzucek made their first contribution in #45
• @tlvince made their first contribution in #13

Full Changelog: v0.2.0...v0.3.0

v0.2.0

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-version can now also accept git refs
• New fail-on option, 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

v0.1.1

0.1.1 - 2022-03-17

This is a patch release for the Slither Action - the Github Action for Slither.

What's Changed:

• Avoid reading .nvmrc during action setup

Full Changelog: v0.1.0...v0.1.1

v0.1.0

0.1.0 - 2022-02-10

This is the first official release of Slither Action - the Github Action for Slither.

Features:

• Support for custom compilation
• Support for different slither version
• Support for different node version
• Github Code Scanning integration