Issue description
As of one hour ago, all of our SLS commands have broken. It seems like the inclusion/exclusion logic changes are causing issues.
the errors pop up for non aws-sdk things too (ex. "semver" or "datadog-lambda-js")
All of our CI is essentially broken :(
Two asks:
- Most important How can we pin to a specific version of serverless? This is the second time now where deployments broke from a bad version release and as far as I can tell, there's no way to turn off the auto updating of serverless4. I already tried pinning to version 4.1.12 in our
package.json but it still installs 4.1.13 under the hood which makes it impossible for us to mitigate this issue ourselves right now. Please tell me if I'm missing something!
- Request to help mitigate the underlying issues in 4.1.13 so we can eventually roll forward
Context
No response
Issue description
As of one hour ago, all of our SLS commands have broken. It seems like the inclusion/exclusion logic changes are causing issues.
the errors pop up for non aws-sdk things too (ex. "semver" or "datadog-lambda-js")
All of our CI is essentially broken :(
Two asks:
package.jsonbut it still installs 4.1.13 under the hood which makes it impossible for us to mitigate this issue ourselves right now. Please tell me if I'm missing something!Context
No response