Kamil Sobol

fix: babel transform of aws-exports.js file when user defined babel configuration

1

#### Description of changes Fixes https://github.com/aws-amplify/amplify-cli/issues/11030 . The fix makes sure that when we call babel we don't take configuration files into account. So that our transform is not affected...

I'm trying to update from `4.2.0` to `7.4.2`. It seems that `license.ts` file gets to npm together with `license.js`. ``` $ ls node_modules/cloudform-types/types/licenseManager/ grant.d.ts index.d.ts index.namespace.d.ts license.d.ts license.ts grant.js index.js...

Check IAM policies for new access

1

## Problem Currently, we rely on PR reviews and unit tests to manage IAM policies. This PR introduces a new mechanism that detects and flags elevation of privilege. The new...

We claim to support Node 18+ (which also includes 20, i.e. latest). We should add some validations in our health checks that assert this works. https://github.com/search?q=repo%3Aaws-amplify%2Famplify-backend+%22engines%22&type=code We should likely: 1....

The instructions for how to deal with e2e tests both in PR and locally seem to be fragmented and are missing some gotchas which became tribal knowledge. We should update...

Follow up from https://github.com/aws-amplify/amplify-backend/pull/1333. We should improve our changeset check to assert that all modified packages are part of md file/files.

Related to: https://github.com/aws-amplify/samsara-cli/issues/554#issuecomment-1791513958 . And https://github.com/aws-amplify/samsara-cli/pull/562 We're adding workaround recommended here https://github.com/aws/aws-cdk/issues/26681#issuecomment-1705232051 . When Lambda serves SDK 3.440.0+ we should remove local SDK bundling. When we do this we should:...

Auth construct doesn't work in opt in region (ap-east-1)

3

### Environment information ```plain text System: OS: macOS 14.3.1 CPU: (10) arm64 Apple M1 Pro Memory: 289.23 MB / 32.00 GB Shell: /bin/bash Binaries: Node: 18.17.1 - /opt/homebrew/opt/node@18/bin/node Yarn: 1.22.21...

Dependency conflict after releasing a breaking change.

2

From https://github.com/aws-amplify/amplify-js-samples-staging/pull/765#discussion_r1436674841 . It appears that releasing a breaking change to `@aws-amplify/plugin-types` does not propagate correctly to `@aws-amplify/backend-cli` that also depends on this transitively. Note that breaking change in `@aws-amplify/plugin-types`...

From https://github.com/aws-amplify/amplify-backend/pull/895#pullrequestreview-1812156772 . And from related PRs https://github.com/aws-amplify/amplify-backend/pull/892 and https://github.com/aws-amplify/amplify-backend/pull/892 . We should revisit how strict do we want to be when asserting versions of packages defined in `amplify-backend` once...