chore(deps): update dependency @aws-amplify/core to v6.11.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@aws-amplify/core (source)	6.10.6 -> 6.11.3

---

Release Notes

aws-amplify/amplify-js (@​aws-amplify/core)

v6.11.3

Compare Source

v6.11.2

Compare Source

v6.11.1

Compare Source

v6.11.0: 2024-12-19 Amplify JS release - aws-amplify@6.11.0

Compare Source

What's Changed

• chore: Merge release into main by @​aws-amplify-ops in https://github.com/aws-amplify/amplify-js/pull/14077
• fix(ci): canary test failure on npm install by @​pranavosu in https://github.com/aws-amplify/amplify-js/pull/14083
• fix(adapter-nextjs): create jwt verifier once by @​erinleigh90 in https://github.com/aws-amplify/amplify-js/pull/13825
• fix(ci): update javascript canary build step by @​pranavosu in https://github.com/aws-amplify/amplify-js/pull/14085
• feat(auth): Enable resumable SignIn (#​13855) by @​joon-won in https://github.com/aws-amplify/amplify-js/pull/14074
• fix(auth): provide NEXT_PUBLIC_BACKEND_CONFIG for resumable mfa E2E by @​joon-won in https://github.com/aws-amplify/amplify-js/pull/14090
• release(required): Amplify JS release by @​Samaritan1011001 in https://github.com/aws-amplify/amplify-js/pull/14091

Full Changelog: https://github.com/aws-amplify/amplify-js/compare/aws-amplify@6.10.3...aws-amplify@6.11.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e98488d

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