The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.
APACHE-2.0 License
Bot releases are visible (Hide)
Published by aws-amplify-ops about 2 years ago
Published by aws-amplify-ops about 2 years ago
All notable changes to this project will be documented in this file.
See Conventional Commits for commit guidelines.
Note: Version bump only for package amplify-prompts
Note: Version bump only for package amplify-prompts
Note: Version bump only for package amplify-prompts
Note: Version bump only for package amplify-prompts
Note: Version bump only for package amplify-prompts
Published by aws-amplify-ops about 2 years ago
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.
Published by aws-amplify-ops about 2 years ago
Published by aws-amplify-ops about 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago
npm install -g @aws-amplify/cli
now downloads a binary executable instead of traversing npm for all dependencies.Benefits:
amplify --version
command, from 1.608s to 1.079s.ua-parser-js
and colors
.Co-authored-by: John Corser [email protected]
Published by aws-amplify-ops over 2 years ago
Published by aws-amplify-ops over 2 years ago