Prepare v0.1.1 npm release

[natanelia]

What changed

• bump ArrowBase from 0.1.0 to 0.1.1 while preserving the existing GitHub-only v0.1.0 release
• publish current compatibility, package, playground, and validation details in release notes
• synchronize README, changelog, release guide, and release contract tests

Why

The existing v0.1.0 GitHub tag points to an older artifact and was never published to npm. v0.1.1 keeps that history immutable and becomes the first public npm release.

Validation

• pnpm release:verify
• pnpm check — 74 files, 714 tests
• pnpm playground:check — 16 files, 80 tests
• pnpm playground:e2e — desktop and mobile
• pnpm build && pnpm verify:package-exports — 6 entry points, 276 callable root exports
• npm pack --dry-run --json — 28 files, 849 KB

Summary by CodeRabbit

• Release

  • Updated the package to version v0.1.1.
  • Marked the first public npm release.
  • Published refreshed release notes covering packaging, compatibility, live queries, spatial indexes, GeoArrow IPC, optimistic transactions, persistence, and cross-tab synchronization.

• Documentation

  • Updated version references and release instructions for v0.1.1.
  • Added updated release validation guidance.

[coderabbitai]

Warning

Review limit reached

@natanelia, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 22e94988-0244-4d73-a3d4-957d66797bce

📥 Commits

Reviewing files that changed from the base of the PR and between 73df6ae and 8424eb0.

📒 Files selected for processing (1)

• docs/RELEASING.md

📝 Walkthrough

Walkthrough

The release is updated from 0.1.0 to 0.1.1 across package metadata, release instructions, documentation, and automated readiness checks. Release notes and changelog entries now describe the 0.1.1 npm release.

Changes

Version 0.1.1 Release Preparation

Layer / File(s)	Summary
Release version and publishing instructions package.json, docs/RELEASING.md	Bumps the package version to 0.1.1 and updates release commands, tarball names, tags, and workflow inputs.
Release metadata and published documentation CHANGELOG.md, README.md, RELEASE_NOTES.md	Adds the 0.1.1 changelog entry and updates release status, highlights, and validation commands.
Release-readiness assertions tests/release-readiness.test.ts	Pins release checks to the 0.1.1 package version, tag, release notes, and changelog entry.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• natanelia/arrowbase#1: Related release-version updates and packaging validation changes.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: preparing the v0.1.1 npm release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/release-0.1.1

---

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

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@RELEASE_NOTES.md`:
- Around line 59-64: Update the Local preflight and Failure rules sections in
docs/RELEASING.md to include both pnpm playground:check and pnpm playground:e2e,
matching the validation checklist in RELEASE_NOTES.md.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7cde3ef7-046f-4ef5-a1d1-a8691c2d46f3

📥 Commits

Reviewing files that changed from the base of the PR and between 0776a9d and 73df6ae.

📒 Files selected for processing (6)

• CHANGELOG.md
• README.md
• RELEASE_NOTES.md
• docs/RELEASING.md
• package.json
• tests/release-readiness.test.ts