Set package version in template to next

[fracek]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request introduces a new JSON metadata file for the "apibara" package and updates the package version constants in the CLI module. The JSON file marks the release as a prerelease with a dependent change type of "patch" and sets the package version to "next." Additionally, version specifications for several dependencies in the CLI’s constants have been updated from "^2.1.0-beta.2" to "next".

Changes

File(s)	Change Summary
change/apibara-7e0b4a31-a40d-4f85-8ee8-a6ca097af7ae.json	Added new JSON file for "apibara" metadata; specifies prerelease type, package name, comment, author email, and a dependent change type set to "patch".
packages/cli/.../constants.ts	Updated packageVersions in the CLI module; changed version specifications for dependencies (apibara, @apibara/indexer, @apibara/protocol, etc.) from "^2.1.0-beta.2" to "next".

Possibly related PRs

• Prepare for release #102: Updates package version specifications to "next", aligning with the changes in this PR.
• indexer: update drizzle and drizzle sink #107: Introduces a new JSON file with prerelease metadata for a related package, similar to this PR.
• Update beta to 2.1.0-beta.x #146: Adjusts version references to "next" for the "apibara" package, which is closely related to the version updates provided here.

Suggested reviewers

• jaipaljadeja

Poem

I'm a rabbit hopping through code all day,
JSON and constants lead the merry way.
From beta to "next", the versions now flow,
With prereleases in metadata, watch our progress grow!
Amid these changes, my bunny heart sings—
In the fields of code, new springtime springs!
🐰💻

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • 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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/cli/src/create/constants.ts (1)

69-79: LGTM! Consider adding a warning comment about using "next" tag.

The changes align with the PR objective to update package versions to "next". However, using the "next" tag means always getting the latest prerelease version, which could lead to:

• Non-deterministic builds
• Potential breaking changes
• Different versions on different machines

Consider adding a warning comment about the implications of using "next":

  // Required Dependencies
+ // WARNING: Using "next" tag will always pull the latest prerelease version.
+ // This is suitable for development/preview but not recommended for production.
  apibara: "next",

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3cf134c and eda8ab6.

📒 Files selected for processing (2)

• change/apibara-7e0b4a31-a40d-4f85-8ee8-a6ca097af7ae.json (1 hunks)
• packages/cli/src/create/constants.ts (1 hunks)

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

• change/apibara-7e0b4a31-a40d-4f85-8ee8-a6ca097af7ae.json