cli: bump @electric-sql/pglite version

[jaipaljadeja]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request introduces several new JSON files containing prerelease metadata for version bumps of the @electric-sql/pglite dependency across multiple packages. It also updates dependency versions in various package.json files and a constants file, shifting from older versions to newer beta versions. Additionally, a configuration file template has been updated to include a new dbCredentials property. All changes are explicitly focused on dependency version updates and metadata enhancements across related packages.

Changes

File(s)	Change Summary
change/*-*.json	New JSON files added for @apibara/indexer, @apibara/plugin-drizzle, and apibara containing prerelease metadata for a version bump of @electric-sql/pglite.
examples/cli/package.json packages/indexer/package.json packages/plugin-drizzle/package.json	Updated @electric-sql/pglite version from ^0.2.14 to ^0.2.17 in the dependency or devDependencies sections.
packages/cli/src/create/constants.ts	Updated the packageVersions object: bumping versions of multiple packages (from beta.40 to beta.42) and updating @electric-sql/pglite to ^0.2.17.
packages/cli/src/create/templates.ts	Modified the configuration export to add a new dbCredentials property with a url set from the POSTGRES_CONNECTION_STRING environment variable.

Sequence Diagram(s)

sequenceDiagram
    participant CLI as Command Line
    participant Generator as createDrizzleStorageFiles
    participant Env as process.env
    participant FS as FileSystem

    CLI->>Generator: Invoke createDrizzleStorageFiles(options)
    Generator->>Env: Read POSTGRES_CONNECTION_STRING
    Generator-->>Generator: Set dbCredentials (default: empty string if not set)
    Generator->>FS: Write updated configuration file
    FS-->>Generator: Configuration file created
    Generator-->>CLI: Return file generation result

Loading

Possibly related PRs

• Fix minor issues with CLI #115: Introduces new JSON files for the apibara package that specify metadata for prerelease versions, related to this PR's focus on versioning.
• feat: add production like example for apibara cli #124: Involves updates to the @electric-sql/pglite dependency, similar to the changes in this PR regarding version bumps.
• cli: include runtime-meta in package #114: Adds new JSON files that specify metadata for the apibara package, relating to versioning aspects similar to this PR.

Suggested reviewers

• fracek

Poem

In a burrow of code I hop,
Bumping versions, I never stop.
JSON files and configs bright,
Guiding our build with delight.
With each dependency in sight,
I celebrate changes through the night!
🐇💕

---

📜 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 3a91df1 and 5c4c8bb.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (8)

• change/@apibara-indexer-2dd5e045-95a9-4fa2-a04a-eda59c8eb237.json (1 hunks)
• change/@apibara-plugin-drizzle-23769ed5-20aa-4c23-88b7-e577eb03748a.json (1 hunks)
• change/apibara-514e91df-c28d-4366-8aba-3bfc8dd41e26.json (1 hunks)
• examples/cli/package.json (1 hunks)
• packages/cli/src/create/constants.ts (1 hunks)
• packages/cli/src/create/templates.ts (1 hunks)
• packages/indexer/package.json (1 hunks)
• packages/plugin-drizzle/package.json (1 hunks)

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

• packages/indexer/package.json
• packages/plugin-drizzle/package.json
• change/apibara-514e91df-c28d-4366-8aba-3bfc8dd41e26.json
• examples/cli/package.json
• change/@apibara-indexer-2dd5e045-95a9-4fa2-a04a-eda59c8eb237.json
• packages/cli/src/create/constants.ts
• change/@apibara-plugin-drizzle-23769ed5-20aa-4c23-88b7-e577eb03748a.json
• packages/cli/src/create/templates.ts

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

• GitHub Check: test

---

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.