Bump serverless from 2.35.0 to 3.0.0

[dependabot]

Bumps serverless from 2.35.0 to 3.0.0.

Release notes

Sourced from serverless's releases.

3.0.0 (2022-01-27)

We are excited to announce the release of Serverless Framework v3!

This new major version brings a cleaner and redesigned CLI experience as well as a brand new feature: stage parameters.

Read all about Serverless Framework v3 in the official blog post.

---

⚠ BREAKING CHANGES

Read the complete v3 Upgrade Guide.

• Variables: Old variables resolver is permanently removed. Any resolution error as approached with current resolver is assumed as final (there's no longer fallback to old resolver)
• AWS Lambda:
  • Default lambda hashing algorithm was changed to 20201221
  • Runtimes nodejs10.x, python2.7, ruby2.5 and dotnetcore2.1 reached end of support on AWS and are no longer recognized in configuration.
  • Default runtime has been changed from nodejs12.x to nodejs14.x
  • Properties service.awsKmsKeyArn and functions[].awsKmsKeyArn are no longer supported. Use provider.kmsKeyArn and functions[].kmsKeyArn instead.
• CLI:
  • CLI params put before command tokens are no longer recgonized (e.g. sls -f <function-name> deploy function will no longer work). In all cases construct CLI args in sls <command> <options> order
  • Unrecognized CLI options will no longer be supported and will result in an error.
  • enableLocalInstallationFallback configuration property is no longer supported.
  • Remove studio command schema
  • The --verbose CLI flag does no longer support -v alias
  • Opt-in tab-tab autocompletion feature is removed due to performance and security issues
• AWS API Gateway:
  • Enabling logs or tracing for imported API Gateway will now result in an error instead of warning
  • For authorizers with request type and caching disabled (resultTtlInSeconds: 0), the identitySource will no longer be set to method.request.header.Authorization by default.
  • Support for usagePlan, resourcePolicy and apiKeys on provider level is removed. Use provider.apiGateway level instead to set them.
  • Support for http.request.schema has been removed and replaced with http.request.schemas.
• AWS HTTP API: Tags from provider.tags are applied by default to HTTP API Gateway.
• AWS CloudFront: Support for MinTTL, MaxTTL, DefaultTTL and ForwardedValues on cloudfront.behavior has been removed.
• AWS EventBridge: By default, EventBridge resources now will be deployed using native CloudFormation resources instead of Custom Resources.
• AWS Alexa: Support for simple alexaSkill event was removed and now appId is required for all alexaSkill events.- Serverless Components (@serverless/components) CLI is no longer integrated with Framework CLI.
• Dashboard: tenant configuration setting is no longer respected. Ensure to rely on org instead
• Serverless Components v1 (@serverless/cli) CLI is no longer integrated with Framework CLI.
• Custom nested configuration paths will no longer be supported and such usage will result in an error.
• Object notation is no longer supported for service property. Set name directly to service.
• When creating Serverless class instance programatically, both options and commands have to be passed via config to the constructor.
• Duplicate plugin definition in configuration will now result in an error instead of a warning.
• Using --aws-s3-accelerate flag will result in an error instead of deprecation when custom S3 bucket is used.
• Removed support for provider.disableDefaultOutputExportNames
• Node.js versions lower than 12 is no longer supported
• Lifecycle events marked as deprecated (in context of v1) are no longer evaluated

Features

... (truncated)

Changelog

Sourced from serverless's changelog.

3.0.0 (2022-01-27)

⚠ BREAKING CHANGES

• Variables: Old variables resolver is permanently removed. Any resolution error as approached with current resolver is assumed as final (there's no longer fallback to old resolver)
• AWS Lambda:
  • Default lambda hashing algorithm was changed to 20201221
  • Runtimes nodejs10.x, python2.7, ruby2.5 and dotnetcore2.1 reached end of support on AWS and are no longer recognized in configuration.
  • Default runtime has been changed from nodejs12.x to nodejs14.x
  • Properties service.awsKmsKeyArn and functions[].awsKmsKeyArn are no longer supported. Use provider.kmsKeyArn and functions[].kmsKeyArn instead.
• CLI:
  • CLI params put before command tokens are no longer recgonized (e.g. sls -f <function-name> deploy function will no longer work). In all cases construct CLI args in sls <command> <options> order
  • Unrecognized CLI options will no longer be supported and will result in an error.
  • enableLocalInstallationFallback configuration property is no longer supported.
  • Remove studio command schema
  • The --verbose CLI flag does no longer support -v alias
  • Opt-in tab-tab autocompletion feature is removed due to performance and security issues
• AWS API Gateway:
  • Enabling logs or tracing for imported API Gateway will now result in an error instead of warning
  • For authorizers with request type and caching disabled (resultTtlInSeconds: 0), the identitySource will no longer be set to method.request.header.Authorization by default.
  • Support for usagePlan, resourcePolicy and apiKeys on provider level is removed. Use provider.apiGateway level instead to set them.
  • Support for http.request.schema has been removed and replaced with http.request.schemas.
• AWS HTTP API: Tags from provider.tags are applied by default to HTTP API Gateway.
• AWS CloudFront: Support for MinTTL, MaxTTL, DefaultTTL and ForwardedValues on cloudfront.behavior has been removed.
• AWS EventBridge: By default, EventBridge resources now will be deployed using native CloudFormation resources instead of Custom Resources.
• AWS Alexa: Support for simple alexaSkill event was removed and now appId is required for all alexaSkill events.- Serverless Components (@serverless/components) CLI is no longer integrated with Framework CLI.
• Dashboard: tenant configuration setting is no longer respected. Ensure to rely on org instead
• Serverless Components v1 (@serverless/cli) CLI is no longer integrated with Framework CLI.
• Custom nested configuration paths will no longer be supported and such usage will result in an error.
• Object notation is no longer supported for service property. Set name directly to service.
• When creating Serverless class instance programatically, both options and commands have to be passed via config to the constructor.
• Duplicate plugin definition in configuration will now result in an error instead of a warning.
• Using --aws-s3-accelerate flag will result in an error instead of deprecation when custom S3 bucket is used.
• Removed support for provider.disableDefaultOutputExportNames
• Node.js versions lower than 12 is no longer supported
• Lifecycle events marked as deprecated (in context of v1) are no longer evaluated

Features

• Variables: Remove old variables resolver (9bf6c16)
• Packaging: Deprecate package.include and package.exclude (aa4f9e3)
• CLI:
  • Deprecate support for deploy -f alias (09c9ea3)
  • Deprecate missing options schema (0db9c49)
  • Deprecate recognition of projectDir configuration setting (00fcd83)
  • Global --debug flag for debug logging (3b4f267)
  • Global --verbose flag for verbose logging (2eef264)
  • Register -v as global --version alias (211db81)
  • Remove -v alias for --verbose flag (03b77c0)
  • Remove support for unrecognized cli options (7c2b2ea)

... (truncated)

Commits

• 16c29da chore: Release v3.0.0
• ad1faa3 chore: Bump dependencies
• c150045 refactor: Rename …nts/api-gateway/lib/method/requestParameters.test.js
• 95e308d refactor: Rename …s/package/compile/events/alb/lib/healthCheck.test.js
• 358a1cf refactor: Rename lib/plugins/aws/package/compile/events/eventBridge
• 88b52ab test: Rename test/integrationPackage
• 3f8b1a1 refactor: Rename …e/compile/events/api-gateway/lib/hack/updateStage.js
• 93d1c29 refactor: Rename …events/api-gateway/lib/hack/disassociateUsagePlan.js
• bb70c63 refactor: Rename …kage/compile/events/websockets/lib/routeResponses.js
• bff4cc7 refactor: Rename …/events/websockets/lib/pickWebsocketsTemplatePart.js
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #138.