Change Log
Summary
This release changes the behavior of how Amplify CLI handles command hooks. If you do not use hooks, this version is not a breaking change. If you do use command hooks, this might be a breaking change.
Previously, command hooks would be uploaded to the S3 deployment bucket on amplify push and pulled down on amplify pull. However, customers who only ran amplify push in CI/CD pipelines would have any new hook changes removed in CI/CD because amplify pull is always executed before amplify push. To fix this issue, Amplify CLI is no longer pushing hooks to the deployment S3 bucket and will not pull down hooks on amplify pull. Instead, hooks should be managed in your VCS system like any other project file.
Additionally, a change has been made to the GraphQL Transformer to enforce stricter validation on custom claims in owner-based auth. Before these changes, non-existent custom claims were allowed and set the default __xamznone__ for the owner claim. After this change, non-existent custom claims will be denied. If your app was relying on this behavior, you may need to update the claims in your auth rules and/or the claims granted by your login flow.
And last but not least, we have overhauled CloudFormation event logs during push. This is not a breaking change but should be a huge quality of life improvement for making sense of deployments.
amplify-category-auth 2.11.0 (2022-09-07)
Features
amplify-category-hosting 3.3.0 (2022-09-07)
Features
amplify-cli 10.0.0 (2022-09-07)
amplify-cli-core 3.0.0 (2022-09-07)
amplify-cli-npm 10.0.0 (2022-09-07)
Features
BREAKING CHANGES
- hooks file management breaking change