chore(deps): bump @radix-ui/react-avatar from 1.1.10 to 1.2.6

[dependabot]

Bumps @radix-ui/react-avatar from 1.1.10 to 1.2.6.

Changelog

Sourced from @​radix-ui/react-avatar's changelog.

1.2.6

• Reverted breaking changes that caused compatibility issues with React Server Components.
• Updated dependencies: @radix-ui/react-context@1.2.2, @radix-ui/react-primitive@2.1.10, @radix-ui/react-use-callback-ref@1.1.4, @radix-ui/react-use-is-hydrated@0.1.3, @radix-ui/react-use-layout-effect@1.1.4

1.2.5

• Updated dependencies: @radix-ui/react-primitive@2.1.9

1.2.4

• Republish through CI to attach provenance attestations. The previous versions of these packages were published manually outside of CI and therefore shipped without provenance; this patch re-releases the same code through the CI pipeline so every package includes an attestation.
• Updated dependencies: @radix-ui/primitive@1.1.7, @radix-ui/react-context@1.2.1, @radix-ui/react-primitive@2.1.8, @radix-ui/react-use-callback-ref@1.1.3, @radix-ui/react-use-is-hydrated@0.1.2, @radix-ui/react-use-layout-effect@1.1.3

1.2.3

• Improved tree-shaking so bundlers can drop unused components. Component parts are now marked /* @__PURE__ */ and use named render functions instead of Component.displayName = ... assignments, which previously prevented dead-code elimination with some bundlers.
• Fix dev-only checks with conditional exports to drop dev-warnings from production builds.
• Updated dependencies: @radix-ui/primitive@1.1.6, @radix-ui/react-context@1.2.0, @radix-ui/react-primitive@2.1.7, @radix-ui/react-use-callback-ref@1.1.2, @radix-ui/react-use-is-hydrated@0.1.1, @radix-ui/react-use-layout-effect@1.1.2

1.2.2

• Updated dependencies: @radix-ui/react-context@1.2.0

1.2.1

• Updated dependencies: @radix-ui/react-primitive@2.1.7

1.2.0

• Fixed several edge cases with Avatar's loading state
  • An avatar's fallback would not be displayed again if its image component unmounted. This is now fixed.
  • Rendering multiple Avatar.Image components per Avatar.Root was never supported and results in buggy, unpredictable behavior. We now warn about this in development.
  • Zero-sized images were treated as loading, meaning that onLoadingStatusChange is never called once loaded. A zero-sized image now triggers an error status on load.

Other updates

• Fixed console warnings to show in test environments.
• Updated dependencies: @radix-ui/react-primitive@2.1.6

1.1.12

• Added repository.directory to all package.json files
• Updated dependencies: @radix-ui/react-context@1.1.4, @radix-ui/react-primitive@2.1.5, @radix-ui/react-use-callback-ref@1.1.2, @radix-ui/react-use-is-hydrated@0.1.1, @radix-ui/react-use-layout-effect@1.1.2

1.1.11

• Updated dependencies: @radix-ui/react-context@1.1.3, @radix-ui/react-primitive@2.1.4

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​radix-ui/react-avatar since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 69cf1a5

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