chore(deps): update dependency solhint to v5 #1096
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. What is protestware?This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function. Consider that consuming this package my come along with functionality unrelated to its primary purpose. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
renovate
bot
force-pushed
the
renovate/solhint-5.x
branch
from
ac38ba4
to
be19b09
Compare
This PR contains the following updates:
4.5.2->5.0.1Release Notes
protofire/solhint (solhint)
v5.0.1Compare Source
BREAKING CHANGES (refer to v5.0.0)
Fixed an issue on the returining values where only was evaluating the first report instead of all of them.
v5.0.0Compare Source
BREAKING CHANGES
Solhint EXIT codes
Solhint changed how the exit codes are implemented:
Exit with 0 codeWhen execution was ok and there were no errors when evaluating the code according to the rulesExit with 1 codeWhen execution was ok and there are errors reportedExit with 1 codeWhen execution was ok and max warnings is lower than the reported warningsExit with 255 codeWhen there's an error in the execution (bad config, writing not allowed, wrong parameter, file not found, etc)Solhint QUIET mode
QUIET mode (-c quiet) option now works with the warnings and may exit with 1 if there are more than defined by user
Thanks to @juanpcapurro for providing the code
v4.5.4Compare Source
Fixed
gas-custom-errorsimproved logic to ranged pragma versions #573gas-indexed-events#573v4.5.3Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.