amplify-backend
amplify-backend copied to clipboard
feat: node compatibility test
Problem
We should be ensuring that our repo is able to install, build, and test using the specified node versions.
Issue number, if available:
Changes
- Update
setup_nodeaction to take innode-versioninput - Add node versions to test matrix in following jobs:
install,build,test_with_coverage - Add node versions to test matrix for
e2e_deployment,e2e_create_amplify - Skip
global.cryptoworkaround for node > 20 as it is no longer needed.
Corresponding docs PR, if applicable:
Validation
Checklist
- [ ] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
- [ ] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
- [ ] If this PR requires a docs update, I have linked to that docs PR above.
- [ ] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the
run-e2elabel set.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
🦋 Changeset detected
Latest commit: be16ddbdc2ec77efe6ffbe46eb494eb12e2fa37c
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 1 package
| Name | Type |
|---|---|
| @aws-amplify/integration-tests | Patch |
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
The checks need to be updated with the new names that includes the matrix configurations post merge