Skip to content

Outage: Version 4.1.13 Breaking Changes (Deployments + Building) #12689

@NicoHinderling

Description

@NicoHinderling

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.

image

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:

  1. 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!
  2. Request to help mitigate the underlying issues in 4.1.13 so we can eventually roll forward

Context

No response

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions