# serverless sf-core@4.41.1 — 4.41.1

- Product: serverless (https://whatsnew.fyi/product/serverless)
- Vendor: serverless
- Date: 2026-08-26
- Version: sf-core@4.41.1
- Original notes: https://github.com/serverless/serverless/releases/tag/sf-core%404.41.1
- Permalink: https://whatsnew.fyi/product/serverless/releases/sf-core-4.41.1

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — Fixed packaging producing a different artifact on every run when using the built-in build system, ensuring artifacts are now byte-for-byte identical across runs
- **fixed** — Fixed `package.patterns` exclusions being ignored in packaged artifacts when using the built-in build system, with negation patterns now honored for both combined-service packaging and `package.individually` mode
- **changed** — Framework-managed custom resources now run on Node.js 24, with deployments using existing S3 buckets, existing Cognito User Pools, EventBridge events, or the API Gateway CloudWatch role picking up the `nodejs24.x` runtime automatically on the next deploy

#### 4.41.1

##### Bug Fixes

- **Fixed packaging producing a different artifact on every run.** When using the built-in build system, repeated `serverless package` runs of an unchanged service produced artifacts with different checksums, so change detection could see phantom diffs and redeploy unchanged services. Artifacts are now byte-for-byte identical across runs. (#13794)

- **Fixed `package.patterns` exclusions being ignored in packaged artifacts.** When using the built-in build system, negation patterns (`!...`) are now honored when packaging function artifacts — both for combined-service packaging and with `package.individually`. Function-level patterns are merged after service-level patterns, so function settings win on conflict, matching classic packaging behavior. (#13795)

##### Maintenance

- **Framework-managed custom resources now run on Node.js 24.** Deployments that use existing S3 buckets, existing Cognito User Pools, EventBridge events, or the API Gateway CloudWatch role pick up the `nodejs24.x` runtime automatically on the next deploy. No action is needed. Thanks @Hiroki-Aoki for raising this! (#13802, #13807)
- Bumped the AWS SDK group with 37 updates (#13796)
- Upgraded esbuild to v0.28.2 (#13798)
- Upgraded tsx to v4.23.11 (#13798)
- Upgraded ws to v8.21.3 (#13798)
- Upgraded eslint to v10.8.1 (#13797)
- Upgraded lint-staged to v17.3.0 (#13797)
- Upgraded hono to v4.13.1 (#13797)
- Upgraded globals to v17.9.0 (#13797)