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

chore: Merge release into main #14077

Merged
merged 4 commits into from
Dec 13, 2024
Merged

chore: Merge release into main #14077

merged 4 commits into from
Dec 13, 2024

Conversation

aws-amplify-ops
Copy link
Collaborator

Merge the recently completed release back into the main development branch. Generated by the callable-npm-publish-release workflow.

pranavosu and others added 4 commits December 12, 2024 14:34
 - @aws-amplify/adapter-nextjs@1.3.0
 - @aws-amplify/analytics@7.0.63
 - @aws-amplify/api@6.1.8
 - @aws-amplify/api-graphql@4.6.6
 - @aws-amplify/api-rest@4.0.63
 - @aws-amplify/auth@6.8.3
 - aws-amplify@6.10.3
 - @aws-amplify/core@6.7.3
 - @aws-amplify/datastore@5.0.65
 - @aws-amplify/datastore-storage-adapter@2.1.65
 - @aws-amplify/geo@3.0.63
 - @aws-amplify/interactions@6.1.4
 - @aws-amplify/notifications@2.0.63
 - @aws-amplify/predictions@6.1.38
 - @aws-amplify/pubsub@6.1.38
 - @aws-amplify/storage@6.7.4
 - tsc-compliance-test@0.1.68
Copy link

⚠️ This PR includes changes to the "aws-amplify" package.json file, which can have library-wide implications.

Please ensure that this PR:

  • Does not manually change "@aws-amplify/*" dependency versions, which may misalign core dependencies across the library
  • Remove any export paths without a major version bump

A repository administrator is required to review this change.

@pranavosu pranavosu merged commit 4b3b13d into main Dec 13, 2024
38 checks passed
@pranavosu pranavosu deleted the temp/release-merge-1734046689 branch December 13, 2024 00:08
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.

5 participants