chore(deps): bump @dicebear/core and @dicebear/collection

[dependabot]

Bumps @dicebear/core and @dicebear/collection. These dependencies needed to be updated together.
Updates @dicebear/core from 7.1.2 to 8.0.1

Release notes

Sourced from @​dicebear/core's releases.

DiceBear 8.0 - Release Notes

A major update with a small fix that changed the output of the avatars in some cases. As soon as a fix changes the output of the avatars, we release a major update to ensure that the avatars of a major version remain consistent. This update is backwards compatible and should not cause any issues.

A bug with random backgrounds has been fixed. These were not consistent between browsers due to their implementation. This problem has been fixed and the backgrounds should now be calculated identically in all browsers.

Further information on this bug can be found in this issue: dicebear/dicebear#394

Changelog

Sourced from @​dicebear/core's changelog.

DiceBear 8.0 - Release Notes

A major update with a small fix that changed the output of the avatars in some cases. As soon as a fix changes the output of the avatars, we release a major update to ensure that the avatars of a major version remain consistent. This update is backwards compatible and should not cause any issues.

A bug with random backgrounds has been fixed. These were not consistent between browsers due to their implementation. This problem has been fixed and the backgrounds should now be calculated identically in all browsers.

Further information on this bug can be found in this issue: dicebear/dicebear#394

Commits

• dc11ff0 v8.0.1
• ed4d875 Change: Update package-lock.json
• 6854209 Fix: randomizeId now uses random hash for real randomness again
• 632d47c Fix: API Version in Editor
• 9901fd5 Change: Update "Host the HTTP API yourself"
• d28682d Fix: CHANGELOG
• 218cf2a v8.0.0
• 7994dac Change: Prepare peer dependencies for 8.x update
• 0b5b33f Fix #394: Different background colours for the same options between browsers.
• f1cb4f9 Change: Update 7.x => 8.x
• See full diff in compare view

Updates @dicebear/collection from 7.1.2 to 8.0.1

Release notes

Sourced from @​dicebear/collection's releases.

DiceBear 8.0 - Release Notes

A major update with a small fix that changed the output of the avatars in some cases. As soon as a fix changes the output of the avatars, we release a major update to ensure that the avatars of a major version remain consistent. This update is backwards compatible and should not cause any issues.

A bug with random backgrounds has been fixed. These were not consistent between browsers due to their implementation. This problem has been fixed and the backgrounds should now be calculated identically in all browsers.

Further information on this bug can be found in this issue: dicebear/dicebear#394

Changelog

Sourced from @​dicebear/collection's changelog.

DiceBear 8.0 - Release Notes

A major update with a small fix that changed the output of the avatars in some cases. As soon as a fix changes the output of the avatars, we release a major update to ensure that the avatars of a major version remain consistent. This update is backwards compatible and should not cause any issues.

A bug with random backgrounds has been fixed. These were not consistent between browsers due to their implementation. This problem has been fixed and the backgrounds should now be calculated identically in all browsers.

Further information on this bug can be found in this issue: dicebear/dicebear#394

Commits

• dc11ff0 v8.0.1
• ed4d875 Change: Update package-lock.json
• 6854209 Fix: randomizeId now uses random hash for real randomness again
• 632d47c Fix: API Version in Editor
• 9901fd5 Change: Update "Host the HTTP API yourself"
• d28682d Fix: CHANGELOG
• 218cf2a v8.0.0
• 7994dac Change: Prepare peer dependencies for 8.x update
• 0b5b33f Fix #394: Different background colours for the same options between browsers.
• f1cb4f9 Change: Update 7.x => 8.x
• See full diff in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.