Skip to content

Conversation

@Adammatthiesen
Copy link
Member

@Adammatthiesen Adammatthiesen commented Apr 20, 2025

Description

  • Closes #
  • What does this PR change? Give us a brief description.

Summary by CodeRabbit

  • Chores
    • Updated dependency versions for several packages to support newer releases and improve compatibility.
    • Loosened version constraints for some packages to allow a broader range of supported versions.

@changeset-bot
Copy link

changeset-bot bot commented Apr 20, 2025

🦋 Changeset detected

Latest commit: fdf08c1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
@studiocms/socialposter Patch
@studiocms/wysiwyg Patch
@studiocms/grapesjs-plugin Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 20, 2025

Walkthrough

This update modifies dependency version constraints in the workspace configuration and a changeset file. The changes include bumping patch versions for several packages such as @astrojs/db, @astrojs/node, @studiocms/blog, @studiocms/devapps, and astro, as well as adjusting the version constraint for studiocms in the minimal catalog section. Additionally, the patch versions for @studiocms/socialposter and @studiocms/wysiwyg are updated to support newer dependency versions. No code logic or exported entities are altered.

Changes

File(s) Change Summary
.changeset/light-carrots-taste.md Updated patch version constraints for @studiocms/socialposter and @studiocms/wysiwyg.
pnpm-workspace.yaml Bumped dependency versions for @astrojs/db, @astrojs/node, @studiocms/blog, @studiocms/devapps, astro, and adjusted studiocms constraint; updated vite version in minimal catalog.

Possibly related PRs

  • Update StudioCMS deps #12: Updates dependency version constraints for @studiocms/socialposter and @studiocms/wysiwyg, targeting the same packages as this PR but includes actual code and metadata changes.

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

@Adammatthiesen Adammatthiesen marked this pull request as ready for review April 20, 2025 06:02
@Adammatthiesen Adammatthiesen requested a review from a team as a code owner April 20, 2025 06:02
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: 0

🧹 Nitpick comments (1)
.changeset/light-carrots-taste.md (1)

6-7: Improve changeset summary clarity
The summary is concise but could list the specific packages and new patch versions to make the change more transparent for future readers.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9990771 and fdf08c1.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • .changeset/light-carrots-taste.md (1 hunks)
  • pnpm-workspace.yaml (1 hunks)
🔇 Additional comments (3)
pnpm-workspace.yaml (2)

17-20: Review minimal catalog version constraints
The studiocms range >=0.1.0-beta.14 may unintentionally allow versions older than the intended patch level, and the vite version was downgraded from ^6.2.6 to ^6.2.5. Confirm that this aligns with the minimal testing strategy.


2-11:

Details

✅ Verification successful

Approve patch-level dependency version bumps in catalog
These updates align with the PR’s objective to allow newer versions. Please verify that the specified versions are published and compatible.


🏁 Script executed:

#!/usr/bin/env bash
# Verify that updated versions exist on npm
packages=(
  "@astrojs/[email protected]"
  "@astrojs/[email protected]"
  "@studiocms/[email protected]"
  "@studiocms/[email protected]"
  "[email protected]"
  "[email protected]"
)
for pkg in "${packages[@]}"; do
  npm view "$pkg" version || echo "Missing version: $pkg"
done

Length of output: 658


🏁 Script executed:

#!/usr/bin/env bash
# Verify that the remaining versions exist on npm
packages=(
  "@astrojs/[email protected]"
  "@types/[email protected]"
  "[email protected]"
  "[email protected]"
)
for pkg in "${packages[@]}"; do
  npm view "$pkg" version || echo "Missing version: $pkg"
done

Length of output: 407


Approve patch-level dependency updates in pnpm-workspace.yaml
All specified versions have been verified on npm and are available as patch-level releases. These updates can be merged.

• File: pnpm-workspace.yaml (lines 2–11)
• Verified versions:

.changeset/light-carrots-taste.md (1)

1-4: Changeset version metadata looks correct
Patch bumps for @studiocms/socialposter and @studiocms/wysiwyg are specified. Ensure these correspond to the actual package.json version increments.

@Adammatthiesen Adammatthiesen merged commit d0f9307 into main Apr 20, 2025
9 checks passed
@Adammatthiesen Adammatthiesen deleted the deps branch April 20, 2025 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants