chore(deps): update architect (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@architect/architect (source)	10.16.3 -> 11.1.0
@architect/functions	5.4.1 -> 8.1.6

---

Release Notes

architect/architect (@​architect/architect)

v11.1.0

Compare Source

Added

• Architect now supports AWS SSO (aws sso login [options]) based workflows; fixes #​1402

Fixed

• Fixed issue where Hydrate fails on projects with only an ASAP root handler, no other Lambdas; fixes #​1491

---

v11.0.13

Compare Source

Added

• Add @aws-lite/client as a dependency of @architect/architect, which should supersede individual package versions

---

v11.0.12

Compare Source

Fixed

• Remove unnecessary legacy validation, including looking for the AWS CLI during deployment; fixes #​1482

---

v11.0.11

Compare Source

Changed

• Updated dependencies
• Updated package.json engines.node property to reflect changes from v11

Fixed

• Fixed potential issues with deployments to projects with a large number of CloudFormation resources; thanks @​w5mix!
• Fixed REST API plugin check; thanks @​jonpacker!

---

v11.0.10

Compare Source

v11.0.9

Compare Source

Fixed

• Fixed Lambda treeshaking of default get /* ASAP handler; thanks @​filmaj!
• Improved detection of local vs global Yarn and pnpm when installing dependencies

---

v11.0.7

Compare Source

Fixed

• env command help uses correct --env, --add, and --remove flags; thanks @​busticated!

---

v11.0.6

Compare Source

Changed

• Updated dependencies

Fixed

• Fixed order of preference for bucket name resolution so passed bucket param can override the ARC_STATIC_BUCKET env var; thanks @​andybee!
• Fixed intermittent issues publishing static assets to S3
• Fixed error destroying an app that did not deploy correctly the first time

---

v11.0.5

Compare Source

Fixed

• Fixed issue where entirely custom Lambda-based projects may error when trying to print the project's URL(s) after deploying

---

v11.0.4

Compare Source

Fixed

• Fixed issue where an unflattened dependency tree in node_modules could result in Node.js issuing a MaxListenersExceededWarning

---

v11.0.3

Compare Source

Architect 11 (Cadborosaurus) is now fully based on aws-lite, and no longer makes use of the AWS SDK or CLI. This dramatically decreases installation time, while massively increasing speed in all AWS operations. Read more about this change at https://arc.codes.

Added

• Added experimental --fast flag, which ships project to AWS without waiting around to determine if the deployment completed successfully. Use with care!
• Improved cross-platform deployment of native modules to arm64 Lambda (the new default in Architect 11)
  • This means any non-arm64 and/or non-Linux machine will now best-effort deploy to arm64 Linux; users are highly encouraged to validate application functionality that relies on native modules
  • This is accomplished by adding the npm --cpu + --os flags, supported by npm v10.1+ – this version of npm is bundled with Node.js 18.19+ or 20.7+
  • If you are using pnpm, Yarn, or a version of npm < v10.1, you must continue to deploy Lambdas to arm64 as before

Changed

• Architect no longer requires or makes use of the AWS SDK and AWS CLI
  • As such, installation, setup, and deployments are all significantly faster
• Breaking change: Sandbox no longer includes aws-sdk + @aws-sdk/* as dependencies
  • Projects that rely on the AWS SDK should install those dependencies to their project directly
  • Consult the Architect upgrade guide for more information
• Breaking change: nodejs20.x and python3.12 are now the default Node.js and Python Lambda runtimes, respectively
  • The Node.js version is not itself a breaking change, however the version of AWS SDK available to your code will change from v2 to v3 – this is entirely an AWS decision, which we are managing as best we can (by way of offering aws-lite as an alternative)
  • For folks who need to continue using AWS SDK v2, simply set @aws runtime nodejs16.x in your project manifest
  • However, be warned: nodejs16.x (and AWS SDK v2 in Lambda) are scheduled for deprecation in a few months
  • Consult the Architect upgrade guide for more information
• Breaking change: arm64 is now the default Lambda architecture
  • This change only impacts projects that utilize native modules or Lambda layers with binaries; projects that make use of regular Node.js packages will not be impacted by this change
• Breaking change: removed support for Node.js 14.x (now EOL, and no longer available to created in AWS Lambda)
• Architect no longer requires the AWS CLI, nor Python. So if you'd like to remove either or both, feel free!
• Deploy no longer writes sam.json + sam.yaml files upon each deploy
  • However, if you do want to see the sam.json being deployed, use the --dry-run or --debug|-d CLI flags
• AWS Lambda no longer supports Go-specific runtimes; as such, go and golang runtime aliases are no longer available
• Added Node.js 20.x to test matrix

Fixed

• Fixed issue where ignoreDependencies would not work if only a single dependency was ignored; thanks @​andybee!
• Fixed issues surrounding correctly toggling @cdn (experimental + undocumented) as enabled or disabled
• Potentially breaking fix: resolved mismatch between RouteSelectionExpression in deployed Architect apps vs. locally in Sandbox
  • The RouteSelectionExpression is now $request.body.action, meaning WebSocket code running locally can now be the same as production code, like so: ws.send(JSON.stringify({ action: 'custom-endpoint', ... }))
  • This fixes #​768; thanks @​mawdesley + @​MartinRamm!
• Fixed issue where treeshaking runs against Lambdas with explicit dependency manifests in cases where those Lambdas were themselves plugins installed as dependencies
• Fixed format of @sandbox-start pragma in preferences (which is preferred to @sandbox-startup)

---

v11.0.2

Compare Source

v11.0.1

Compare Source

Added

• Add @aws-lite/client as a dependency of @architect/architect, which should supersede individual package versions

---

v11.0.0

Compare Source

Architect 11 (Cadborosaurus) is now fully based on aws-lite, and no longer makes use of the AWS SDK or CLI. This dramatically decreases installation time, while massively increasing speed in all AWS operations. Read more about this change at https://arc.codes.

Added

• Added experimental --fast flag, which ships project to AWS without waiting around to determine if the deployment completed successfully. Use with care!
• Improved cross-platform deployment of native modules to arm64 Lambda (the new default in Architect 11)
  • This means any non-arm64 and/or non-Linux machine will now best-effort deploy to arm64 Linux; users are highly encouraged to validate application functionality that relies on native modules
  • This is accomplished by adding the npm --cpu + --os flags, supported by npm v10.1+ – this version of npm is bundled with Node.js 18.19+ or 20.7+
  • If you are using pnpm, Yarn, or a version of npm < v10.1, you must continue to deploy Lambdas to arm64 as before

Changed

• Architect no longer requires or makes use of the AWS SDK and AWS CLI
  • As such, installation, setup, and deployments are all significantly faster
• Breaking change: Sandbox no longer includes aws-sdk + @aws-sdk/* as dependencies
  • Projects that rely on the AWS SDK should install those dependencies to their project directly
  • Consult the Architect upgrade guide for more information
• Breaking change: nodejs20.x and python3.12 are now the default Node.js and Python Lambda runtimes, respectively
  • The Node.js version is not itself a breaking change, however the version of AWS SDK available to your code will change from v2 to v3 – this is entirely an AWS decision, which we are managing as best we can (by way of offering aws-lite as an alternative)
  • For folks who need to continue using AWS SDK v2, simply set @aws runtime nodejs16.x in your project manifest
  • However, be warned: nodejs16.x (and AWS SDK v2 in Lambda) are scheduled for deprecation in a few months
  • Consult the Architect upgrade guide for more information
• Breaking change: arm64 is now the default Lambda architecture
  • This change only impacts projects that utilize native modules or Lambda layers with binaries; projects that make use of regular Node.js packages will not be impacted by this change
• Breaking change: removed support for Node.js 14.x (now EOL, and no longer available to created in AWS Lambda)
• Architect no longer requires the AWS CLI, nor Python. So if you'd like to remove either or both, feel free!
• Deploy no longer writes sam.json + sam.yaml files upon each deploy
  • However, if you do want to see the sam.json being deployed, use the --dry-run or --debug|-d CLI flags
• AWS Lambda no longer supports Go-specific runtimes; as such, go and golang runtime aliases are no longer available
• Added Node.js 20.x to test matrix

Fixed

• Fixed issue where ignoreDependencies would not work if only a single dependency was ignored; thanks @​andybee!
• Fixed issues surrounding correctly toggling @cdn (experimental + undocumented) as enabled or disabled
• Potentially breaking fix: resolved mismatch between RouteSelectionExpression in deployed Architect apps vs. locally in Sandbox
  • The RouteSelectionExpression is now $request.body.action, meaning WebSocket code running locally can now be the same as production code, like so: ws.send(JSON.stringify({ action: 'custom-endpoint', ... }))
  • This fixes #​768; thanks @​mawdesley + @​MartinRamm!
• Fixed issue where treeshaking runs against Lambdas with explicit dependency manifests in cases where those Lambdas were themselves plugins installed as dependencies
• Fixed format of @sandbox-start pragma in preferences (which is preferred to @sandbox-startup)

---

architect/functions (@​architect/functions)

v8.1.6

Compare Source

v8.1.5

Compare Source

v8.1.3

Compare Source

v8.1.2

Compare Source

v8.1.1

Compare Source

v8.1.0

Compare Source

v8.0.4

Compare Source

v8.0.3

Compare Source

v8.0.2

Compare Source

v8.0.1

Compare Source

v8.0.0

Compare Source

v7.0.0

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.