Bump crytic/slither-action from 0.1.1 to 0.3.0

[dependabot]

Bumps crytic/slither-action from 0.1.1 to 0.3.0.

Release notes

Sourced from crytic/slither-action's releases.

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 crytic/slither-action#45
• Add stdout output by @​tlvince in crytic/slither-action#13
• Mark git repositories as safe inside the slither-action container by @​elopez in crytic/slither-action#50
• Enable pipefail by @​elopez in crytic/slither-action#51

New Contributors

Thanks to the new contributors in this release!

• @​jporzucek made their first contribution in crytic/slither-action#45
• @​tlvince made their first contribution in crytic/slither-action#13

Full Changelog: crytic/slither-action@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 crytic/slither-action#12
• @​0xCLARITY made their first contribution in crytic/slither-action#27

... (truncated)

Commits

• 6ef3a33 Update references to other actions in README
• bdeb26c Fix README heading level
• ce84f97 Update action version on README
• f7d9645 Merge pull request #51 from crytic/dev-pipefail
• cac9c4f Enable pipefail
• 67b91ad Merge pull request #50 from crytic/dev-git-safe-workspace
• fda5e39 Mark git repositories as safe inside the slither-action container
• 11878ab Merge pull request #13 from tlvince/feat/stdout
• 072b1fe Update to new multiline syntax and recent action changes
• 8183bb8 Merge remote-tracking branch 'origin/dev' into feat/stdout
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Dependabot tried to add @fedekunze and @khoslaventures as reviewers to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/Canto-Network/Canto-Testnet/pulls/74/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the Canto-Network/Canto-Testnet repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request