feat: upgrading future development and testing of this plugin exclusively to Serverless v3 #284
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit c779fdd.
Bumps [axios](https://github.com/axios/axios) and @serverless/platform-client. These dependencies needed to be updated together. Updates `axios` from 0.21.4 to 1.6.2 - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v0.21.4...v1.6.2) Updates `@serverless/platform-client` from 4.4.0 to 4.5.1 --- updated-dependencies: - dependency-name: axios dependency-type: indirect - dependency-name: "@serverless/platform-client" dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…vely to Serverless v3 Upgrading this to Serverless v3. I haven't changed any behavior or code to do this so I expect this will continue to work with Serverless v2, but I do not plan to test against Serverless v2 going forward. The tests have been using Serverless v3 for some time now per https://github.com/activescott/serverless-aws-static-file-handler/blame/c779fdd93662784c1a7b651057764d64734b13fb/examples/serverless-offline/package.json#L16 so this should be of negligible impact. So why? The serverless community is focused on the v3 version at this point and Serverless v2 brings along a few vulnerability warnings due to it's outdated dependencies that I'd prefer to not ignore.
activescott
force-pushed
the
feat/serverless-v3
branch
from
30f605a
to
e1cbbc0
Compare
|
🎉 This PR is included in version 4.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrading this to Serverless v3. I haven't changed any behavior or code to do this so I expect this will continue to work with Serverless v2, but I do not plan to test against Serverless v2 going forward. The tests have been using Serverless v3 for some time now per https://github.com/activescott/serverless-aws-static-file-handler/blame/c779fdd93662784c1a7b651057764d64734b13fb/examples/serverless-offline/package.json#L16 so this should be of negligible impact.
So why? The serverless community is focused on the v3 version at this point and Serverless v2 brings along a few vulnerability warnings due to it's outdated dependencies that I'd prefer to not ignore.