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)