Bump @architect/architect from 9.5.4 to 10.8.2

[dependabot]

Bumps @architect/architect from 9.5.4 to 10.8.2.

Changelog

Sourced from @​architect/architect's changelog.

[10.8.1 - 10.8.2] 2022-12-05

Fixed

• Fixed hydrate.copy API bug where files are copied to vendor, not node_modules, for typescript Lambdas
• Fixed hydrate.copy API bug where Lambda build dir is not used

---

[10.8.0] 2022-11-30

Added

• Added support for Lambda's new nodejs18.x runtime, and AWS SDK v3 (@aws-sdk/*)
  • @architect/functions + @architect/asap now also have full support for SDK v3
  • If your Lambdas make use of @architect/functions (and you otherwise do not directly rely on AWS SDK calls), you are now fully forward-compatible with nodejs18.x
    • Your upgrade path is installing @architect/functions >= 5.3
  • However, if your Lambdas do NOT make use of @architect/functions, before opting into Lambda nodejs18.x + SDK v3 we strongly advise you read: https://arc.codes/aws-sdk-versions
  • To opt in, simply change your @aws runtime setting to nodejs18.x (learn more at http://arc.codes/docs/en/reference/project-manifest/aws#runtime)
• Added Node.js 18.x to test coverage

Changed

• nodejs16.x (which still uses SDK v2) is now the default Node.js runtime, bumped from nodejs14.x
  • Because 18.x only includes SDK v3, this is a breaking change, and will remain an opt-in until a future major release of Architect
• In order to paper over breaking changes in AWS SDK v2 to v3, @architect/functions + @architect/asap inspect the running Node.js version to follow different code paths to corresponding SDK versions; if your test / CI environment is not using the same Node.js version as your production environment, this may result in unexpected testing issues
  • For example: your CI environment runs Node.js 18.x, but your Lambda uses @architect/functions >= 5.3 and is configured to use 16.x; some methods deep within the SDK may differ, and your tests may break
  • Unless you are making use of arc.tables()._db + arc.tables()._doc, we think this scenario is pretty unlikely. That said, this is unfortunately not something Architect can control for or prevent, and ultimately falls to AWS to resolve for developers
  • We can only strongly advise your CI and production environments use the same version of Node.js

Fixed

• Fixed issue where Sandbox, running via Node.js 18.x, may fail to respond to local requests from the same host in Node.js <= 16.x

---

[10.7.3] 2022-11-15

Changed

• Changed hydrate.copy API to copy files into all Lambdas, not just those with shared code enabled

Fixed

• Fixed issue where hydrate.copy plugins breaking on projects that disabled or aren't using shared code; thanks @​tbeseda!
• Ensure Sandbox CLI interface can be called with quiet option
• Fixed issue where projects with plugins that define >1 transpiled (read: runtime typescript) Lambdas would all build to the same directory; thanks @​Scorsi!

... (truncated)

Commits

• d57ea43 10.8.2
• ec62004 Update deps and changelog
• 1e84d3a 10.8.1
• 2b2fa96 Update deps and changelog
• fef2b37 10.8.0
• 10076b4 Update deps and changelog
• 5d3384e 10.8.0-RC.0
• 2633cad Update deps and changelog
• 940a271 Add Node.js 18.x to test matrix
• 147da7a 10.7.3
• 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 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]

Superseded by #63.