chore: add publish script

[ymc9]

Summary by CodeRabbit

• Chores
  • Added a new script to publish all packages with the "next" tag.
  • Updated the preview publish script to include the "next" tag.

[coderabbitai]

Walkthrough

A new "publish-all" script was added to the package.json to publish all packages with the npm tag "next." Additionally, the "publish-preview" script was updated to include the "--tag next" option, while the "unpublish-preview" script remains unchanged.

Changes

File	Change Summary
package.json	Added "publish-all" script for publishing all packages with tag "next"; updated "publish-preview" to include "--tag next".

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant NPM Scripts
    participant NPM Registry

    Developer->>NPM Scripts: Run "publish-all"
    NPM Scripts->>NPM Registry: Publish all packages with tag "next"

    Developer->>NPM Scripts: Run "publish-preview"
    NPM Scripts->>NPM Registry: Publish all packages with tag "next" (force, custom registry)

Loading

Possibly related PRs

• chore: add publish/unpublish preview scripts #19: Modifies the same npm scripts in package.json, extending the publish-preview script and adding a related publish-all script.

Poem

A rabbit hops with nimble feet,
New scripts to make our publish neat!
"All" and "preview" tagged as "next",
Our packages now are quite well-dressed.
With every hop, a version grows—
To npm lands, the rabbit goes!
🐇✨

---

📜 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 1cda530 and a3baaee.

📒 Files selected for processing (1)

• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: build-test (20.x)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (actions)

🔇 Additional comments (2)

package.json (2)

11-11: Add publish-all script for tagging next releases

This new script correctly publishes all packages under ./packages/** with the next tag, aligning with the release workflow.

---

12-12: Include --tag next in publish-preview script

The publish-preview script is now updated to tag preview publishes as next, which matches the intended npm workflow.

---

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.
  • @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 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

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 generate sequence diagram to generate a sequence diagram of the changes in 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.