Bump serverless from 3.38.0 to 4.2.4

[dependabot]

Bumps serverless from 3.38.0 to 4.2.4.

Release notes

Sourced from serverless's releases.

4.2.1

Serverless Framework version 4.2.1 now offers experimental support for AWS SAM (Serverless Application Model) and CloudFormation templates. The reason: medium-to-large organizations are seeking to consolidate tools to standardize workflows and simplify development. They don't want multiple serverless frameworks, they just want one.

Get started with SAM and Cloudformation in Serverless Framework by reading the docs.

With this initial release, Serverless Framework enables you to deploy new or existing SAM or CloudFormation projects, without requiring modifications to your existing configuration files. Simply take your raw SAM or CF file in YAML or JSON, and the Serverless Framework will handle the deployment seamlessly.

Serverless Framework will auto-detect SAM/Cloudformation projects in template.yml. You can also provide a custom template file name. We've enabled initial support for samconfig.toml configuration properties that are specific to deployment.

Further, we've enabled support for Serverless Framework's popular Serverless Variables, enabling you to add them directly into SAM and CF syntax. Here are the Serverless Variables that are supported in SAM/CFN templates, with many more coming:

• AWS Account ID: ${aws:accountId}
• AWS Region: ${aws:region}
• AWS Stack Output: ${cf:another-service-dev.functionPrefix}
• CLI Options: ${opt:<option>}
• SLS Instance ID: ${sls:instanceId}
• Environment Variables: ${env:ENV_VAR}
• File: ${file(./myCustomFile.yml)}
• Git: ${git:<variable>}
• S3: ${s3:myBucket/myKey}
• SSM: ${ssm:/path/to/service/id}

Looking ahead, our focus will be on integrating SAM and CloudFormation templates into Serverless Compose files, allowing you to deploy traditional Serverless Framework, SAM, and CloudFormation projects together. Additionally, you will be able to set stage-based configuration Variables that all project files can inherit, as well as share security policies, observability configuration, and more—bringing you closer to a fully consolidated, streamlined workflow.

4.1.23

This is another Serverless Framework V.4 GA release. If you have Serverless Framework V.4 installed already, it will auto-update within 24 hours, or you can run serverless update to get the latest version immediately. If you are upgrading to V.4 from V.3 or less, see our Upgrading to Serverless Framework V.4 Documentation.

Bug Fixes

• Fix dotenv loading, serverless/serverless#12760

4.1.22

This is another Serverless Framework V.4 GA release. If you have Serverless Framework V.4 installed already, it will auto-update within 24 hours, or you can run serverless update to get the latest version immediately. If you are upgrading to V.4 from V.3 or less, see our Upgrading to Serverless Framework V.4 Documentation.

Bug Fixes

• Remove process scoped temp folders and make a new temp folder per framework run - fixes: serverless/serverless#12749
• Backwards compatibility with v3 progress spinners

4.1.19

This is another Serverless Framework V.4 GA release. If you have Serverless Framework V.4 installed already, it will auto-update within 24 hours, or you can run serverless update to get the latest version immediately. If you are upgrading to V.4 from V.3 or less, see our Upgrading to Serverless Framework V.4 Documentation.

Bug Fixes

• Fixes region resolution - serverless/serverless#12721
• Bring back aws-profile CLI option - serverless/serverless#12717

4.1.17

This is another Serverless Framework V.4 GA release. If you have Serverless Framework V.4 installed already, it will auto-update within 24 hours, or you can run serverless update to get the latest version immediately. If you are upgrading to V.4 from V.3 or less, see our Upgrading to Serverless Framework V.4 Documentation.

... (truncated)

Changelog

Sourced from serverless's changelog.

Changelog

All notable changes to this project will be documented in this file. See standard-version for commit guidelines.

Commits

• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)