👷 [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.5.0

Minor Changes

• #29 e8d1b1f Thanks @renovate! - Update web-vitals to 5.1.0

Summary by CodeRabbit

• Chores
  • Bumped @studiocms/web-vitals package version to 4.5.0 to align with web-vitals 5.1.0.
  • Removed an obsolete changeset entry related to the dependency update.
• Documentation
  • Added a changelog entry for version 4.5.0 noting the update to web-vitals 5.1.0.

No functional or API changes; this release is metadata and documentation only.

[coderabbitai]

📝 Walkthrough

Walkthrough

Removes a changeset entry proposing a minor update, adds a 4.5.0 entry to the web-vitals package changelog, and bumps packages/web-vitals/package.json version from 4.4.1 to 4.5.0. No code or API changes.

Changes

Cohort / File(s)	Summary of Changes
Changeset cleanup /.changeset/mighty-masks-doubt.md	Deleted a changeset proposing a minor bump for @studiocms/web-vitals to 5.1.0.
Web-vitals release metadata /packages/web-vitals/CHANGELOG.md, /packages/web-vitals/package.json	Added changelog entry for 4.5.0 noting web-vitals 5.1.0 update; bumped package version from 4.4.1 to 4.5.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• 👷 [ci]: Ready for Release #11 — Similar release metadata edits for @studiocms/web-vitals (package.json and changelog updates, changeset adjustments).
• 👷 [ci]: Ready for Release #18 — Updates versioning and changelog for the same package with changeset modifications.
• 👷 [ci]: Ready for Release #22 — Changeset deletions plus package.json and CHANGELOG updates for @studiocms/web-vitals.

Suggested reviewers

• Adammatthiesen
• louisescher

Poem

A hop and a bump to four-point-five,
I twitch my whiskers—docs arrive.
No code disturbed, just numbers neat,
Carrots tall, releases sweet.
Changelog sung, the fields are bright—
Ship it quick, then moonlit night. 🥕✨

---

📜 Recent review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between dfa6778 and c56780d.

📒 Files selected for processing (3)

• .changeset/mighty-masks-doubt.md (0 hunks)
• packages/web-vitals/CHANGELOG.md (1 hunks)
• packages/web-vitals/package.json (1 hunks)

💤 Files with no reviewable changes (1)

• .changeset/mighty-masks-doubt.md

🔇 Additional comments (2)

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

3-8: Changelog and package.json versions are consistent

The 4.5.0 entry in packages/web-vitals/CHANGELOG.md matches the version in package.json, and the web-vitals dependency is correctly bumped to ^5.1.0. All checks pass—ready to merge.

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

4-4: Version bump to 4.5.0 is correct and matches the changelog.

No other manifest changes; dependency on web-vitals is at ^5.1.0 as advertised. Good to release.

✨ 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

---

🪧 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.
  • 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.
• 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 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/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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@32

commit: 7394cfc