chore(deps): update @rslib/core to 1.0.0-beta.1

[elecmonkey]

Summary

Bump the @rslib/core catalog entry from ~1.0.0-beta.0 to ~1.0.0-beta.1. beta.1 has breaking changes, but after careful inspection they do not affect the correctness of the build output.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 49 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ce67d880-391e-4737-b907-3fb444deeffb

📥 Commits

Reviewing files that changed from the base of the PR and between 692a728 and 1945045.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• pnpm-workspace.yaml

📝 Walkthrough

Walkthrough

Updated the workspace catalog entry for @rslib/core from ~1.0.0-beta.0 to ~1.0.0-beta.1.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the dependency bump, though it omits that the workspace uses a tilde range.
Description check	✅ Passed	The description matches the change and explains the version bump and its impact.
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 chore/update-rslib-beta1

---

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]

🧹 Nitpick comments (1)

pnpm-workspace.yaml (1)

18-18: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Pin beta.1 exactly if it is the supported contract.

~1.0.0-beta.1 permits later 1.0.0 prereleases and stable 1.0.x releases when the lockfile is regenerated. Since @rslib/core is dynamically invoked and re-exported by rstack, use 1.0.0-beta.1 if these changes must be adopted only after explicit review; otherwise document and test the intended compatibility policy. Semver defines this tilde range as >=1.0.0-beta.1 <1.1.0-0. (github.com)

🤖 Prompt for 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.

In `@pnpm-workspace.yaml` at line 18, Update the `@rslib/core` dependency
declaration in pnpm-workspace.yaml from the tilde range to the exact supported
version 1.0.0-beta.1, ensuring later prerelease or stable releases are not
selected during lockfile regeneration.

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

Nitpick comments:
In `@pnpm-workspace.yaml`:
- Line 18: Update the `@rslib/core` dependency declaration in pnpm-workspace.yaml
from the tilde range to the exact supported version 1.0.0-beta.1, ensuring later
prerelease or stable releases are not selected during lockfile regeneration.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 002ea3a0-2a72-4cf2-964b-2cf117c49333

📥 Commits

Reviewing files that changed from the base of the PR and between 82a944f and 692a728.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• pnpm-workspace.yaml

[elecmonkey]

The catalog uses ~1.0.0-beta.1. Since beta releases can carry breaking changes within minor version, and Rstack is already used by some production projects, should this better be pinned to the exact 1.0.0-beta.1?

[cloudflare-workers-and-pages]

Deploying rstack-cli with    Cloudflare Pages

Latest commit:	1945045
Status:	⚡️  Build in progress...

View logs