Skip to content
New issue

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

pin amplify-category-api to 5.12.10 #14116

Closed
wants to merge 2 commits into from
Closed

Conversation

bobbyu99
Copy link
Contributor

@bobbyu99 bobbyu99 commented Feb 21, 2025

Description of changes

Pin amplify-category-api to 5.12.10 so that API Gen1 canaries and e2e install 5.12.10 and not 5.13.0.

Description of how you validated changes

Checklist

  • PR description included
  • yarn test passes
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)
  • New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
  • Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@bobbyu99 bobbyu99 requested a review from a team as a code owner February 21, 2025 00:09
@bobbyu99 bobbyu99 marked this pull request as draft February 21, 2025 01:15
Copy link
Member

@sobolk sobolk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ^ in amplify-category-api is intentional.

When we build CLI release we're using a version from yarn.lock. Which currently points 5.12.10.

The purpose of ^ is that when jobs in category-api repo install cli-internal then the cli is compatible with any new version of category-api. So that you can run cli with category api release that is about to ship.

If you need to pin category api in your e2e tests, that should be happening in category api repo, not here.

@bobbyu99 bobbyu99 closed this Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants