👷 [ci]: Ready for Release (experimental)

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

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@studiocms/[email protected]

Patch Changes

• #12 848df9e Thanks @Adammatthiesen! - Update StudioCMS to beta.15

• #10 e8325a2 Thanks @Adammatthiesen! - fix: remove redundant call to read Response object

• #12 848df9e Thanks @Adammatthiesen! - Minimum required StudioCMS version is now beta.15

@studiocms/[email protected]

Patch Changes

• #12 848df9e Thanks @Adammatthiesen! - Update StudioCMS to beta.15

• Updated dependencies []:

  • @studiocms/[email protected]

@studiocms/[email protected]

Summary by CodeRabbit

• Chores

  • Expanded internal update tracking with additional entries.
  • Released experimental version 0.1.0-experimental.2 across multiple modules.
  • Improved dependency alignment with the latest StudioCMS beta release and streamlined performance.

• Documentation

  • Refreshed release notes to clearly highlight the experimental release and its refinements.

[coderabbitai]

Walkthrough

This pull request updates the configuration and release documentation. The .changeset/pre.json file's changesets array is expanded to include three new entries. The @studiocms/socialposter, @studiocms/grapesjs-plugin, and @studiocms/wysiwyg packages have new entries in their changelogs for version 0.1.0-experimental.2, documenting various updates, including dependency changes and version updates in their respective package.json files. No changes were made to exported or public entities.

Changes

File(s)	Change Summary
.changeset/pre.json	Expanded changesets array to include five entries: "blue-buses-doubt", "fifty-taxes-rhyme", "strong-dancers-crash".
packages/studiocms_socialposter/CHANGELOG.md packages/studiocms_socialposter/package.json	Added release note for version 0.1.0-experimental.2, updating StudioCMS to beta.15 and removing a redundant Response call; updated package version.
packages/studiocms_grapesjs-plugin/CHANGELOG.md packages/studiocms_grapesjs-plugin/package.json	Added release note for version 0.1.0-experimental.2; updated package version.
packages/studiocms_wysiwyg/CHANGELOG.md packages/studiocms_wysiwyg/package.json	Added release note for version 0.1.0-experimental.2, referencing a pull request and commit for StudioCMS update; updated package version.

Possibly related PRs

• 👷 [ci]: Ready for Release (experimental) #3: Modifies the same .changeset/pre.json file with changes to the changesets array.
• 👷 [ci]: Ready for Release (experimental) #9: Involves updates to the changesets array in .changeset/pre.json.

Suggested reviewers

• Adammatthiesen

---

📜 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 6c43d76 and f3c5e9f.

📒 Files selected for processing (7)

• .changeset/pre.json (1 hunks)
• packages/studiocms_grapesjs-plugin/CHANGELOG.md (1 hunks)
• packages/studiocms_grapesjs-plugin/package.json (1 hunks)
• packages/studiocms_socialposter/CHANGELOG.md (1 hunks)
• packages/studiocms_socialposter/package.json (1 hunks)
• packages/studiocms_wysiwyg/CHANGELOG.md (1 hunks)
• packages/studiocms_wysiwyg/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (4)

• packages/studiocms_grapesjs-plugin/package.json
• packages/studiocms_wysiwyg/package.json
• packages/studiocms_grapesjs-plugin/CHANGELOG.md
• packages/studiocms_wysiwyg/CHANGELOG.md

🚧 Files skipped from review as they are similar to previous changes (3)

• .changeset/pre.json
• packages/studiocms_socialposter/CHANGELOG.md
• packages/studiocms_socialposter/package.json

---

🪧 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 plan to trigger planning for file edits and PR creation.
• @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/experiments/@studiocms/grapesjs-plugin@11

npm i https://pkg.pr.new/withstudiocms/experiments/@studiocms/socialposter@11

npm i https://pkg.pr.new/withstudiocms/experiments/@studiocms/wysiwyg@11

commit: 6c43d76

[dreyfus92]

🚢