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(main): release 1.0.4 #962

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 31, 2024

🤖 I have created a release beep boop

1.0.4 (2025-01-13)

Bug Fixes

  • deps: update dependency caniuse-lite to v1.0.30001676 (0194fe1)
  • deps: update dependency caniuse-lite to v1.0.30001677 (98dd6f8)
  • deps: update dependency caniuse-lite to v1.0.30001678 (377c90e)
  • deps: update dependency caniuse-lite to v1.0.30001679 (#969) (ad17a6c)
  • deps: update dependency caniuse-lite to v1.0.30001680 (#970) (b7a816d)
  • deps: update dependency caniuse-lite to v1.0.30001683 (#980) (fe5ea1d)
  • deps: update dependency caniuse-lite to v1.0.30001684 (#982) (3890d17)
  • deps: update dependency caniuse-lite to v1.0.30001686 (#990) (5b454ad)
  • deps: update dependency caniuse-lite to v1.0.30001687 (#996) (483b808)
  • deps: update dependency qs to v6.13.1 (#975) (b2cf99b)
  • deps: update dependency swagger-ui-react to v5.18.0 (#965) (2d279b6)

This PR was generated with Release Please. See documentation.

Copy link

vercel bot commented Oct 31, 2024

Deployment failed with the following error:

Resource is limited - try again in 43 minutes (more than 100, code: "api-deployments-free-per-day").

Copy link

changeset-bot bot commented Oct 31, 2024

⚠️ No Changeset found

Latest commit: dc8fb3f

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.

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

Copy link

coderabbitai bot commented Oct 31, 2024

Important

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.


Note

Free review on us!

CodeRabbit is offering free reviews until Wed Jan 15 2025 to showcase some of the refinements we've made.

🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from 7ef5f86 to ab9b1a4 Compare November 1, 2024 16:28
Copy link

vercel bot commented Nov 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-validations ❌ Failed (Inspect) Jan 13, 2025 2:53am
next-validations-demo ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 13, 2025 2:53am

@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from ab9b1a4 to 43756da Compare November 2, 2024 21:40
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from 43756da to fec03dd Compare November 4, 2024 02:03
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from fec03dd to e4f0779 Compare November 5, 2024 15:26
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from e4f0779 to 1d3918e Compare November 5, 2024 16:04
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from 1d3918e to 6819f33 Compare November 6, 2024 01:46
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from 6819f33 to 526f3a3 Compare November 7, 2024 07:03
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from 526f3a3 to f94ca57 Compare November 7, 2024 10:00
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from f94ca57 to 873c15c Compare November 8, 2024 06:53
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from f7f34f4 to a35a40d Compare December 28, 2024 22:16
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from a35a40d to de0b42d Compare January 2, 2025 22:56
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from de0b42d to d910384 Compare January 6, 2025 02:31
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from d910384 to 60df5af Compare January 7, 2025 20:51
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from 60df5af to d74e612 Compare January 8, 2025 20:43
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from d74e612 to 93baad6 Compare January 9, 2025 05:09
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from 93baad6 to 835a507 Compare January 10, 2025 00:54
@github-actions github-actions bot force-pushed the release-please--branches--main--components--next-validations branch from 835a507 to 3e40253 Compare January 12, 2025 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants