Skip to content

👷 [ci]: Ready for Release#37

Merged
Adammatthiesen merged 1 commit intomainfrom
changeset-release/main
Aug 26, 2025
Merged

👷 [ci]: Ready for Release#37
Adammatthiesen merged 1 commit intomainfrom
changeset-release/main

Conversation

@studiocms-no-reply
Copy link
Member

@studiocms-no-reply studiocms-no-reply commented Aug 26, 2025

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

Patch Changes

Summary by CodeRabbit

  • Chores
    • Published a patch release (v4.5.2) for the Web Vitals package with updated release metadata.
  • Documentation
    • Updated the changelog to reflect the new patch release.
  • Bug Fixes
    • No user-facing fixes in this release.
  • Notes
    • No functional changes; behavior and public API remain unchanged.

@studiocms-no-reply studiocms-no-reply requested a review from a team as a code owner August 26, 2025 08:19
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 26, 2025

📝 Walkthrough

Walkthrough

Removes a changeset entry, adds a 4.5.2 patch entry to packages/web-vitals/CHANGELOG.md referencing build/test script updates, and bumps packages/web-vitals/package.json version from 4.5.1 to 4.5.2. No code or API changes.

Changes

Cohort / File(s) Summary
Release metadata update (web-vitals)
packages/web-vitals/CHANGELOG.md, packages/web-vitals/package.json
Add 4.5.2 changelog patch entry (docs about buildkit/test scripts); bump version 4.5.1 → 4.5.2.
Changeset cleanup
.changeset/little-trees-heal.md
Remove patch release entry and note; no additions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • Adammatthiesen
  • louisescher

Poem

I thump the ground—patch hop, hop, hooray!
Changelog petals bloom in tidy array.
Version nibble: 4.5.2, neat and sweet.
Changeset crumbs swept under my feet.
Build kits packed, tests snug as can be—
A rabbit signs the release with glee. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ 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
Copy link

pkg-pr-new bot commented Aug 26, 2025

Open in StackBlitz

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

commit: 35cdc04

Copy link
Contributor

@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: 1

🧹 Nitpick comments (1)
packages/web-vitals/package.json (1)

4-4: Optional: declare supported Node engines to match Astro 5 baseline.

Consider adding an engines field (e.g., Node >=18.18) to prevent installs on unsupported runtimes. Low-effort guardrail, especially for CI consumers.

   "license": "MIT",
+  "engines": {
+    "node": ">=18.18"
+  },
📜 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 de51086 and 35cdc04.

📒 Files selected for processing (3)
  • .changeset/little-trees-heal.md (0 hunks)
  • packages/web-vitals/CHANGELOG.md (1 hunks)
  • packages/web-vitals/package.json (1 hunks)
💤 Files with no reviewable changes (1)
  • .changeset/little-trees-heal.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-08-10T07:38:46.762Z
Learnt from: Adammatthiesen
PR: withstudiocms/web-vitals#20
File: .github/workflows/ci-push-main.yml:110-110
Timestamp: 2025-08-10T07:38:46.762Z
Learning: The withstudiocms/web-vitals repository is being used as a test environment for new workflows before implementing them across other withstudiocms repositories.

Applied to files:

  • packages/web-vitals/CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Pkg-pr-new Snapshot Release
🔇 Additional comments (3)
packages/web-vitals/package.json (2)

4-4: LGTM: Version bump to 4.5.2 aligns with a patch-only release.

No runtime, API, or dependency changes detected here—safe to publish.


4-4: Sanity checks passed: version and CHANGELOG are in sync and no pending changesets found.

All required checks have succeeded for packages/web-vitals:

  • package.json version (4.5.2) matches a ## 4.5.2 entry in CHANGELOG.md
  • No unreleased changesets reference @studiocms/web-vitals

You can proceed with merging.

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

3-8: LGTM: 4.5.2 entry is well-formed and scoped as Patch.

Formatting matches prior sections; links and attribution look consistent with repo conventions.

@Adammatthiesen Adammatthiesen merged commit e3a4b18 into main Aug 26, 2025
13 of 14 checks passed
@Adammatthiesen Adammatthiesen deleted the changeset-release/main branch August 26, 2025 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants