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.1.9 #262

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

Conversation

nito-bot[bot]
Copy link
Contributor

@nito-bot nito-bot bot commented Jul 26, 2024

🤖 I have created a release beep boop

1.1.9 (2025-02-26)

Bug Fixes

  • deps: update dependency @astrojs/check to v0.8.3 (4e885a1)
  • deps: update dependency @astrojs/check to v0.9.0 (b0ffecc)
  • deps: update dependency @astrojs/check to v0.9.1 (131ea10)
  • deps: update dependency @astrojs/check to v0.9.2 (791a9a9)
  • deps: update dependency @astrojs/check to v0.9.3 (d8df5be)
  • deps: update dependency @astrojs/check to v0.9.4 (1fb7403)
  • deps: update dependency astro to v4.12.3 (e2fa695)
  • deps: update dependency astro to v4.13.0 (32ca5c2)
  • deps: update dependency astro to v4.13.1 (a67b971)
  • deps: update dependency astro to v4.13.2 (75594e6)
  • deps: update dependency astro to v4.13.3 (90a122c)
  • deps: update dependency astro to v4.13.4 (246fdd4)
  • deps: update dependency astro to v4.14.0 (51fa6ca)
  • deps: update dependency astro to v4.14.1 (10de9dd)
  • deps: update dependency astro to v4.14.2 (b58e2a3)
  • deps: update dependency astro to v4.14.3 (ad5c65c)
  • deps: update dependency astro to v4.14.4 (cb05d0d)
  • deps: update dependency astro to v4.14.5 (7974423)
  • deps: update dependency astro to v4.14.6 (82946a4)
  • deps: update dependency astro to v4.15.0 (85caf05)
  • deps: update dependency astro to v4.15.1 (930a0c9)
  • deps: update dependency astro to v4.15.10 (e9334ee)
  • deps: update dependency astro to v4.15.11 (8eb481a)
  • deps: update dependency astro to v4.15.12 (fdb139d)
  • deps: update dependency astro to v4.15.2 (936e0f1)
  • deps: update dependency astro to v4.15.3 (d0f00e3)
  • deps: update dependency astro to v4.15.4 (1ec8daa)
  • deps: update dependency astro to v4.15.5 (dc626b0)
  • deps: update dependency astro to v4.15.6 (05e0b2d)
  • deps: update dependency astro to v4.15.7 (e5a44c5)
  • deps: update dependency astro to v4.15.8 (3450799)
  • deps: update dependency astro to v4.15.9 (97680f7)
  • deps: update dependency astro to v4.16.0 (59acd29)
  • deps: update dependency astro to v4.16.1 (381fbee)
  • deps: update dependency astro to v4.16.10 (5990c99)
  • deps: update dependency astro to v4.16.11 (#346) (4cba4fe)
  • deps: update dependency astro to v4.16.12 (#347) (130b32f)
  • deps: update dependency astro to v4.16.13 (#348) (21f61b5)
  • deps: update dependency astro to v4.16.14 (#352) (6666d7b)
  • deps: update dependency astro to v4.16.15 (#356) (19c4da6)
  • deps: update dependency astro to v4.16.16 (#358) (0682dea)
  • deps: update dependency astro to v4.16.17 (#363) (68921b1)
  • deps: update dependency astro to v4.16.18 (#367) (824229c)
  • deps: update dependency astro to v4.16.2 (2fe49ad)
  • deps: update dependency astro to v4.16.3 (e12840a)
  • deps: update dependency astro to v4.16.4 (594aaae)
  • deps: update dependency astro to v4.16.5 (eea34cd)
  • deps: update dependency astro to v4.16.6 (8c66021)
  • deps: update dependency astro to v4.16.7 (d23b391)
  • deps: update dependency astro to v4.16.8 (9423c95)
  • deps: update dependency astro to v4.16.9 (8b47780)

This PR was generated with Release Please. See documentation.

Copy link

coderabbitai bot commented Jul 26, 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.

Walkthrough

The project has transitioned from version 1.1.8 to 1.1.9, indicating updates in dependency management and bug fixes. Notable upgrades include the @astrojs/check package to version 0.9.3 and the astro package incremented to version 4.15.1. These changes are documented in the updated changelog.

Changes

File Change Summary
.github/release-please-manifest.json, CHANGELOG.md, package.json Version updated from 1.1.8 to 1.1.9. The changelog includes bug fixes and updates: @astrojs/check to 0.9.3 and astro to 4.15.1.

Poem

🐰 In the garden where bugs do dwell,
A hop for fixes, all is well!
Dependencies bloom, in colors bright,
Upgrading softly, a joyful sight.
With every change, our code takes flight! 🐇✨


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
🪧 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.
  • @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.

Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://56c5842e.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 8be0fa1 to 699a210 Compare July 27, 2024 10:49
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://9fa17843.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 699a210 to aa96079 Compare July 30, 2024 16:29
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://60fa9210.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from aa96079 to 2e4811e Compare July 31, 2024 14:13
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://72473443.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 2e4811e to b791f38 Compare July 31, 2024 16:31
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://7049a62f.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from b791f38 to 04374fe Compare August 1, 2024 10:54
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://df89d96e.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 04374fe to e19f482 Compare August 2, 2024 15:45
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://566e265d.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from e19f482 to 2fed7c4 Compare August 6, 2024 17:30
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://b9a5065b.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 791a9a9 and 2fed7c4.

Files selected for processing (3)
  • .github/release-please-manifest.json (1 hunks)
  • CHANGELOG.md (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (3)
  • .github/release-please-manifest.json
  • CHANGELOG.md
  • package.json

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 2fed7c4 to 8655d89 Compare August 7, 2024 23:38
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://af65c415.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2fed7c4 and 8655d89.

Files selected for processing (3)
  • .github/release-please-manifest.json (1 hunks)
  • CHANGELOG.md (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (2)
  • CHANGELOG.md
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .github/release-please-manifest.json

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 8655d89 to 2af2251 Compare August 8, 2024 13:08
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://6120c325.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8655d89 and 2af2251.

Files selected for processing (3)
  • .github/release-please-manifest.json (1 hunks)
  • CHANGELOG.md (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • CHANGELOG.md
Files skipped from review as they are similar to previous changes (2)
  • .github/release-please-manifest.json
  • package.json

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 2af2251 to 84bfc98 Compare August 9, 2024 22:41
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://b4e68eae.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2af2251 and 84bfc98.

Files selected for processing (3)
  • .github/release-please-manifest.json (1 hunks)
  • CHANGELOG.md (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • CHANGELOG.md
Files skipped from review as they are similar to previous changes (2)
  • .github/release-please-manifest.json
  • package.json

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 84bfc98 to d95784d Compare August 14, 2024 00:39
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://6f0e7811.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 84bfc98 and d95784d.

Files selected for processing (3)
  • .github/release-please-manifest.json (1 hunks)
  • CHANGELOG.md (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • CHANGELOG.md
Files skipped from review as they are similar to previous changes (2)
  • .github/release-please-manifest.json
  • package.json

Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://bc67195a.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from d8f207d to f6599a3 Compare January 20, 2025 18:06
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://58971ac5.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from f6599a3 to 5a95ec2 Compare January 22, 2025 17:59
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://df762bb1.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 5a95ec2 to de83ce2 Compare January 24, 2025 21:43
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://a5aee9db.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from de83ce2 to 670cb4a Compare January 28, 2025 01:31
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://db17b713.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 670cb4a to 9153a22 Compare January 31, 2025 01:42
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://9f7e1771.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 9153a22 to e55e701 Compare February 1, 2025 21:45
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://e2ec5b0d.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from e55e701 to 60e531f Compare February 2, 2025 08:48
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://4f702075.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 60e531f to 16278bc Compare February 4, 2025 01:36
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://77a14e40.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 16278bc to 0ba1272 Compare February 10, 2025 20:54
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://e7fb8875.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 0ba1272 to 9f1b123 Compare February 15, 2025 02:47
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://cff5fc68.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from 9f1b123 to d4da385 Compare February 17, 2025 06:57
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://842968e8.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from d4da385 to e353de8 Compare February 22, 2025 10:47
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://16e36ff5.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

@nito-bot nito-bot bot force-pushed the release-please--branches--main--components--nito.club branch from e353de8 to 9e15085 Compare February 26, 2025 12:29
Copy link
Contributor Author

@nito-bot nito-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device URL
mobile https://5d2368aa.nito-club.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

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