We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why did you guys move runtime condition without major version bump? Isn't this a breaking change ?
My tests started to fail with right after you guys shipped. I do have ^ here https://github.com/aws-amplify/amplify-cli/blob/f5cebf532894bf4a22d9f938933c38fc4f8e4b1a/packages/amplify-category-custom/resources/package.json#L13 . I would expect that when you ship minor or patch version increment my environment doesn't just break.
^
error [email protected]: The engine \"node\" is incompatible with this module. Expected version \">= 14.18.0\".
Looks like it went out here #1611 .
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Why did you guys move runtime condition without major version bump? Isn't this a breaking change ?
My tests started to fail with right after you guys shipped. I do have
^
here https://github.com/aws-amplify/amplify-cli/blob/f5cebf532894bf4a22d9f938933c38fc4f8e4b1a/packages/amplify-category-custom/resources/package.json#L13 . I would expect that when you ship minor or patch version increment my environment doesn't just break.Looks like it went out here #1611 .
The text was updated successfully, but these errors were encountered: