This is a non-blocking issue, but we just had a whole lot of automated PRs request we upgrade our serverless dependency from 3.* -> 4.* from Snyk due to 2+ vulnerabilities at a medium priority and I think one was high priority (resolved moving from 3.22.0 -> 3.38.0).
Does the serverless-deploy pipe Docker image typically stay up to date with npm vulnerabilities on the serverless package? Thanks!
@Sam Mahr hi. We have a plan to upgrade serverless-deploy pipe to Serverless 4.*
We will notify you when new version will become available.
Regards, Igor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sam Mahr
We have done investigation and according to the critical breaking changes in the Serverless Framework V4 we will not upgrade to v4 soon:
- Deprecation Of Non-AWS Providers
- License Changes
- extra layer for Authentication Via Access Or License Keys
The serverless-deploy pipe was designed for deploy to a multi-cloud providers at first.
Best regards,
Oleksandr Kyrdan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.