chore: sync npm package versions

[findolor]

Motivation

The npm release run successfully published @rainlanguage/raindex@0.0.1-alpha.239, then failed because @rainlanguage/ui-components@0.0.1-alpha.238 was already published. The repository remained one version behind both registry versions, so rerunning the workflow unchanged would collide on the raindex version as well.

Failed run: https://github.com/rainlanguage/raindex/actions/runs/29427021691/job/88374580976

Solution

• Synchronize the committed raindex version to 0.0.1-alpha.239.
• Synchronize the committed UI-components version to 0.0.1-alpha.238.
• Point UI components at raindex 0.0.1-alpha.239.
• Update the corresponding workspace entries in package-lock.json.

Checks

• Parsed the manifests and lockfile with Node and asserted all six version relationships.
• git diff --check
• Commit hooks passed, including no-consumer-prettier and prettier-rainix.

Summary by CodeRabbit

• Chores
  • Published updated alpha versions of the Raindex and UI components packages.
  • Updated the UI components package to depend on the latest Raindex alpha release.

[findolor]

• chore: sync npm package versions #2815 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label Raindex-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5710299f-a546-4fe5-988a-e73cf64bbf50

📥 Commits

Reviewing files that changed from the base of the PR and between 3fa0041 and 57cd07b.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• packages/raindex/package.json
• packages/ui-components/package.json

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

• packages/ui-components/package.json

---

📝 Walkthrough

Walkthrough

The Raindex package version is bumped to 0.0.1-alpha.239. UI Components is bumped to 0.0.1-alpha.238 and updates its Raindex dependency accordingly.

Changes

Package release alignment

Layer / File(s)	Summary
Align package versions and dependency packages/raindex/package.json, packages/ui-components/package.json	Raindex and UI Components package versions are incremented, and UI Components now depends on Raindex 0.0.1-alpha.239.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: thedavidmeister

🚥 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 accurately describes the main change: synchronizing npm package versions.
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 arda/sync-npm-package-versions

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install timed out. The project may have too many dependencies for the sandbox.

---

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

[graphite-app]

Merge activity

• Jul 20, 3:43 PM UTC: findolor added this pull request to the Graphite merge queue.
• Jul 20, 3:57 PM UTC: Merged by the Graphite merge queue.

[github-actions]

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

• Simple bug fixes, typos, or minor refactoring
• Single-purpose changes affecting 1-2 files
• Documentation updates
• Configuration tweaks
• Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

• Fix typo in variable name
• Update README with new instructions
• Adjust configuration values
• Simple one-line bug fixes
• Import statement cleanup

Medium (M)

Characteristics:

• Feature additions or enhancements
• Refactoring that touches multiple files but maintains existing behavior
• Breaking changes with backward compatibility
• Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

• Add new feature or component
• Refactor common utility functions
• Update dependencies with minor breaking changes
• Add new component with tests
• Performance optimizations
• More complex bug fixes

Large (L)

Characteristics:

• Major feature implementations
• Breaking changes or API redesigns
• Complex refactoring across multiple modules
• New architectural patterns or significant design changes
• Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

• Complete new feature with frontend/backend changes
• Protocol upgrades or breaking changes
• Major architectural refactoring
• Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

• Test coverage impact: More comprehensive test changes lean toward larger classification
• Risk level: Changes to critical systems bump up a size category
• Team familiarity: Novel patterns or technologies increase complexity

Notes:

• the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
• the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
• do not include any additional text, only the size classification
• your assessment comment must not include tips or additional sections
• do NOT tag me or anyone else on your comment

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

base_ref="$(git merge-base HEAD origin/main 2>/dev/null || git merge-base HEAD main)"
git diff --stat "$base_ref"...HEAD
printf '\n--- changed files ---\n'
git diff --name-status "$base_ref"...HEAD
printf '\n--- diff summary ---\n'
git diff --numstat "$base_ref"...HEAD

Length of output: 484

---

SIZE=S