👷 [ci]: Ready for Release

[studiocms-no-reply]

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

@studiocms/web-vitals@4.3.0

Minor Changes

• #15 32c0bf8 Thanks @Adammatthiesen! - Updates deps to support @astrojs/db ^0.16.1

Summary by CodeRabbit

• Chores
  • Updated dependencies to support @astrojs/db version ^0.16.1.
  • Bumped package version to 4.3.0.
  • Updated changelog to reflect the latest dependency update.

[coderabbitai]

Walkthrough

A changeset file documenting a minor dependency update for @studiocms/web-vitals was deleted. The CHANGELOG.md and package.json for the package were updated to reflect a new version (4.3.0) supporting @astrojs/db version ^0.16.1. No code or public API changes were made.

Changes

Cohort / File(s)	Change Summary
Remove Changeset Record .changeset/slick-bears-work.md	Deleted changeset markdown file documenting a minor dependency update.
Update Changelog packages/web-vitals/CHANGELOG.md	Added entry for version 4.3.0 noting dependency update to support @astrojs/db ^0.16.1.
Version Bump packages/web-vitals/package.json	Updated package version from 4.2.1 to 4.3.0; no other metadata or dependency changes.

Sequence Diagram(s)

(No sequence diagram generated; changes are limited to metadata and documentation.)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update dependencies to support @astrojs/db ^0.16.1 #15: Directly related—introduces the same dependency update to support @astrojs/db ^0.16.1.
• Update deps due to latest Astro updating zod #10: Related—previous dependency version update for @studiocms/web-vitals involving @astrojs/db.
• update deps and file cleanup #8: Related—adds a changeset and updates dependencies for the same package, though for different versions.

Suggested reviewers

• Adammatthiesen

Poem

A bunny hopped through versioned trails,
Updating numbers, leaving changelog tales.
Out with the changeset, in with the new,
Dependencies freshened, as rabbits do.
No code disturbed, just a tidy sweep—
Version 4.3.0, a promise to keep!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 32c0bf8 and 4c89d9c.

📒 Files selected for processing (3)

• .changeset/slick-bears-work.md (0 hunks)
• packages/web-vitals/CHANGELOG.md (1 hunks)
• packages/web-vitals/package.json (1 hunks)

💤 Files with no reviewable changes (1)

• .changeset/slick-bears-work.md

🔇 Additional comments (2)

packages/web-vitals/package.json (1)

4-4: Version bump looks correct and consistent

The minor bump to 4.3.0 is in line with the dependency-only change and matches the semantic-versioning policy applied throughout the project.

packages/web-vitals/CHANGELOG.md (1)

3-8: Changelog accurately reflects the release content

The new 4.3.0 entry clearly documents the dependency update and references the originating PR/commit. No issues spotted.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changeset-release/main

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests 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.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/withstudiocms/web-vitals/@studiocms/web-vitals@16

commit: 4c89d9c