Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump @architect/functions from 4.1.1 to 5.3.1 #115

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 1, 2022

Bumps @architect/functions from 4.1.1 to 5.3.1.

Changelog

Sourced from @​architect/functions's changelog.

[5.3.1] 2022-11-30

Fixed

  • Fixed issue where users without the AWS-SDK installed locally or globally would error if @architect/functions is required or imported

[5.3.0] 2022-11-24

Added

  • Added support for Lambda's new nodejs18.x runtime, and AWS SDK v3 (@aws-sdk/*)
    • If your Lambdas make use of @architect/functions (and you otherwise do not directly rely on AWS SDK calls), you are now likely fully forward-compatible with nodejs18.x (see caveats below)
    • 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 upgrade @architect/architect to 10.8 and 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

  • Due to changes in AWS SDK v2 → v3, arc.tables()._db + arc.tables()._doc methods are now slightly different; unfortunately, this is not something @architect/functions can paper over; see more here
  • In order to paper over breaking changes in AWS SDK v2 to v3, @architect/functions 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
  • Updated dependencies

[5.2.3] 2022-10-14

Changed

  • Updated dependencies

Fixed

  • Fixed double-encoding issue for arc.http[async] responses that are already base64-encoded

[5.2.2] 2022-09-07

Changed

  • Updated dependencies

... (truncated)

Commits
  • e365252 5.3.1
  • b17ec01 Ensure SNS/SQS are required only when needed
  • 77d1973 5.3.0
  • 2657e19 Update deps and changelog
  • 35ec0f2 Un-restore Node.js 12.x from test matrix; test deps need 14+
  • ede01a4 Restore some tests for !nodejs18.x
  • e63e9ec Restore Node.js 12 to test matrix
  • 9299806 5.2.4-RC.0
  • 1731151 adds switching logic to ws methods
  • 8800038 Remove logging statements
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [@architect/functions](https://github.com/architect/functions) from 4.1.1 to 5.3.1.
- [Release notes](https://github.com/architect/functions/releases)
- [Changelog](https://github.com/architect/functions/blob/main/_changelog.md)
- [Commits](architect/functions@v4.1.1...v5.3.1)

---
updated-dependencies:
- dependency-name: "@architect/functions"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 1, 2022
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 13, 2022

Superseded by #117.

@dependabot dependabot bot closed this Dec 13, 2022
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/architect/functions-5.3.1 branch December 13, 2022 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants