chore(deps-dev): bump serverless from 3.38.0 to 4.4.0

[dependabot[bot]]

Bumps serverless from 3.38.0 to 4.4.0.

Release notes

Sourced from serverless's releases.

4.4.0

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.

Features:

• Adds support for SAM & CF in Serverless Compose
• Adds support for serverless info command for SAM & CF

Bugs:

• Fixed serverless/serverless#12778 - serverless deploy function with a custom docker image fails
• Fixed serverless/serverless#12799 - sls deploy started throwing following error since last 2 days: str2.indexOf is not a function
• Fixed issue with serverless remove with failing dependencies.

4.3.2

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.

In this release we introducing the AWS AI Stack, a full-stack, serverless, boilerplate for AI applications on AWS and to support this new project we fixed some bugs and added some new major features to Serverless Compose.

Features:

• Adds support for new global Compose sub-commands.
• Adds support for remote state storage for Serverless Framework Compose & Traditional.
• Adds support for centralized deployment buckets.

Bugs:

• Fixes support for Compose sub-commands

4.2.5

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.

Features

• Added esbuild-package:package hooks to lifecycle events.

Bug Fixes

• Fixed error reporting issue with SAM/CF support.
• Fixed package.patterns bug when used with build.esbuild.
• Fixed bug that improperly showed Axiom progress bar.

4.2.4

Hidden costs in AWS Lambda deployments can quickly add up, particularly from logs, metrics, and traces. These expenses often catch teams by surprise, impacting budgets and operational efficiency.

That’s where Axiom comes in—a standout observability solution that combines a sleek user experience with competitive pricing and an impressive free tier offering 500GB/month of data ingestion.

‍We’re excited to introduce Axiom’s integration with the Serverless Framework. With a simple, one-line configuration in your serverless.yml file, you can easily enhance your monitoring capabilities without breaking the bank.

Cost Comparison Switching from AWS CloudWatch to Axiom can lead to substantial cost savings due to the significant price difference between the two services:

• Axiom: $0.15/GB of ingested data
• AWS CloudWatch: $0.50/GB of ingested data

... (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

• d132d4f docs(sam): add info docs (#12814)
• f57e521 fix(deploy-function): do not set Runtime if function PackageType is Image (#1...
• ac6a536 docs(sam): add compose (#12811)
• dc8d517 feat(sam): docs updates for SAM & Compose (#12788)
• a12a2bd fix: revert to original signature of getServerlessDeploymentBucketName (#12801)
• e76c9c4 chore: add AI stack to readme features
• 72e45ee docs: minor formatting updates (#12795)
• 36297e6 docs(state): add docs on compose state (#12780)
• ce78e85 docs: deployment bucket (#12793)
• 4887554 fix: avoid creating deployment bucket when unnecessary (#12794)
• 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 show 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)

[dependabot[bot]]

Superseded by #574.