[ci] release

[Fryuni]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@inox-tools/[email protected]

Minor Changes

• 2e64078: Use stable Astro APIs

Summary by CodeRabbit

• Chores
  • Upgraded the testing package to version 0.5.0 to enhance overall stability.
• Documentation
  • Revised the release log to reflect the update and clarify the continued use of stable Astro APIs.

[vercel]

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

Name	Status	Preview	Updated (UTC)
inox-tools	✅ Ready (Inspect)	Visit Preview	Feb 27, 2025 4:33pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request removes the file .changeset/late-dogs-grab.md, which previously documented a minor version bump and guidance for using stable Astro APIs for @inox-tools/astro-tests. In its place, the changelog in packages/astro-tests/CHANGELOG.md now includes a new version entry (0.5.0) with the same note, and the version in packages/astro-tests/package.json is updated from 0.4.0 to 0.5.0.

Changes

Files	Change Summary
.changeset/late-dogs-grab.md	Removed the file that contained a changelog entry for a minor version update and a note to "Use stable Astro APIs" for @inox-tools/astro-tests.
packages/astro-tests/CHANGELOG.md, packages/astro-tests/package.json	Added a new version entry (0.5.0) in the changelog and updated the version number in package.json for @inox-tools/astro-tests to reflect the minor change.

Possibly related PRs

• feat(astro-tests): Use stable Astro Config APIs #203: The changes in the main PR involve the removal of the .changeset/late-dogs-grab.md file, while the retrieved PR adds an entry to the same file, indicating a direct conflict in their modifications, thus they are related.
• [ci] release #177: The changes in the main PR, which involve the removal of a version entry for the @inox-tools/astro-tests package, are related to the retrieved PR as both involve updates to the @inox-tools/astro-tests package, specifically regarding versioning and the use of stable Astro APIs.
• [ci] release #197: The changes in the main PR, which involve the removal of a changelog entry for the @inox-tools/astro-tests package, are related to the changes in the retrieved PR that also include a changelog entry for the same package, indicating a minor version update. Both PRs address versioning and changelog modifications for @inox-tools/astro-tests.

Poem

I'm a happy bunny, hopping with delight,
Version bumps and changelogs make my day bright.
Removed old notes, now new entries bloom,
My whiskers twitch as I celebrate in the room.
With a little hop and a joyful code dance,
I cheer for updates—here's to a better chance!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2e64078 and 8ced854.

📒 Files selected for processing (3)

• .changeset/late-dogs-grab.md (0 hunks)
• packages/astro-tests/CHANGELOG.md (1 hunks)
• packages/astro-tests/package.json (1 hunks)

---

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>, 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.