chore(deps): update aws-amplify version.

[osama-rizk]

Description of changes

Updated aws-amplify peer dependency from ^6.14.3 to ^6.16.0 across all packages in the monorepo to ensure version consistency and prevent dependency conflicts for end users. Also updated the aws-amplify version in the root package.json.

Files updated:

• Root package.json (both peer dependency and regular dependency)
• All package-specific package.json files (React, Vue, Angular, React Native, and related packages)
• Updated yarn.lock to reflect dependency changes

This change aligns all packages to use the same aws-amplify version, following monorepo best practices.

Issue #, if available

N/A - Maintenance update to align aws-amplify versions

Description of how you validated changes

• Verified all package.json files now reference aws-amplify: "^6.16.0"
• Confirmed root package.json aws-amplify version updated to ^6.16.0
• Confirmed yarn.lock was properly updated
• No breaking changes expected as this is a minor version bump within the same major version range

Checklist

• Have read the Pull Request Guidelines
• PR description included
• yarn test passes and tests are updated/added
• PR title and commit messages follow conventional commit syntax
• If this change should result in a version bump, changeset added (This can be done after creating the PR.) This does not apply to changes made to docs, e2e, examples, or other private packages.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: f37b67e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ahmedhamouda78]

Is it safe to use caret versioning here? The previous version was specifically pinned.

[osama-rizk]

I used the pinned version.

[ahmedhamouda78]

Any reason we need to change this (i.e. hot-fix, etc.)? I am asking because the caret versioning we had before should install the latest minor version by default while being backwards compatible with versions all the way to 6.14.3.

This question also applies to the other package.json files.

[bobbor]

@ahmedhamouda78 this is due to version resolution in the yarn.lock

if it resolves to (let's say) 6.14.5 it fulfills ^6.14.3 and would never bump the version (unless major release as you say).

deleting the yarn.lock (or at least the aws-amplify segments) would do the trick

[osama-rizk]

deleting the yarn.lock

I deleted yarn.lock and re-install.

[bobbor]

short question:

have you tried simply removing all yarn.lock files and then reinstalling all dependencies?
that should unpin the resolved versions and achieve the same as without updating every single amplify dependency.