chore: update snyk netlify plugin for newer version

[lirantal]

Thanks for contributing the Netlify plugins directory!

Are you adding a plugin or updating one?

• Adding a plugin
• Updating a plugin

Have you completed the following?

• Read and followed the plugin author guidelines.
• Included all required fields in your entry.
• Tested the plugin locally and on Netlify, using the plugin version stated in your entry.

Test plan

Yes, this plugin has been bumped as it has received a few updates and this PR is to keep it up to date.

[lirantal]

What is the proper way to use the updated version of a module in a Netlify build so I can indeed test in there?

[ehmicky]

Hey @lirantal 👋

You can test a specific version of your plugin by installing it in package.json (as opposed to installing it via the UI). This works both for CLI builds and UI builds. Please let me know if I understood your question correctly.

This update is removing the severity plugin input. This would be a breaking change since builds fail when users specify unknown plugin inputs. There are two possible solutions:

• Add the severity plugin input back to manifest.yml, but only for backward compatibility, i.e. the plugin's code would not use that input anymore. This could be completely removed from manifest.yml on the next major release.
• Make a major release.

I would personally recommend the first option since it might be simpler, what do you think?

[lirantal]

Thanks @ehmicky
Where do you see that it makes a change to the severity plugin input? Mostly this update is due to fixing a typo in the plugin and requiring a newer snyk CLI version underlying this plugin that wraps it. Makes sense?

[ehmicky]

The change is here coming from this commit.

One situation which could happen for some of your users is: if they use the severity input, their builds will now start failing with an error message indicating that severity is an unknown input.

Fortunately, it is possible to make a major release to ensure this breaking change does not break those users' sites. Alternatively, it is also possible to add the severity input back, if this change was accidental.

What do you think?