Repository navigation
Conversation
The open-ended >= range lets solid-js 2.0.0 satisfy the peer once it is released, but these adapters are built for Solid 1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWMMJ6aTSA3MvtgJWG2
🦋 Changeset detectedLatest commit: 6379521 The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Update peer dependency range packages/charts-core/package.json, packages/solid-charts/package.json, .changeset/solid-js-peer-cap.md, benchmarks/conformance/previews/manifest.json |
Both package manifests change the solid-js peer dependency range to ^1.8. The changeset records patch releases for both packages. The conformance preview manifest has an updated sourceHash; its asset entries remain unchanged. |
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Bug fix
Possibly related PRs
- TanStack/charts#246: Adds a separate Solid 2 adapter entry while preserving the Solid 1 entry.
Suggested reviewers: greglum
Merge Risk: 
Minimal · up to 486ae
-
The scoped peer-range and manifest updates present no identified merge-blocking risk.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
|
Thanks Ryan, this catches an important compatibility gap. The lockfile needs the matching change before this can land.
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks Tanner. Updated the lockfile specifier for |
|
Thanks Ryan, the lockfile correction checks out. The updated file matches the locally verified correction. This is now waiting on approval for the Conformance and Benchmarks workflows. |
|
Thanks Ryan. I completed the full-checkout verification at The install left every tracked file unchanged. This adds independent full-workspace and package evidence to the earlier peer-range and lockfile checks. The two GitHub workflows still need approval, so this remains unmerged. |
|
View your CI Pipeline Execution ↗ for commit 9e28cbd
☁️ Nx Cloud last updated this comment at |
There was a problem hiding this comment.
Nx Cloud is proposing a fix for your failed CI:
We fixed both failing checks by formatting pnpm-lock.yaml with Prettier and refreshing the source hash in the catalog previews manifest.json. The hash covers the lockfile and packages/charts-core/package.json, both of which this PR changed. With the hash updated, format-check and catalog-preview-check should now pass.
Warning
- ❌ We could not verify this fix.
- The suggested diff is too large to display here, but you can view it on Nx Cloud ↗
Or Apply changes locally with:
npx nx-cloud apply-locally umUI-v9CL
Apply fix locally with your editor ↗ View interactive diff ↗
🎓 Learn more about Self-Healing CI on nx.dev
|
Thanks Ryan. The formatting and preview conflict are fixed on this branch, and the updated checks are ready for workflow approval.
|
🎯 Changes
The Solid packages here declare an open-ended
solid-jspeer (>=1.x). Solid 2.0.0 is due shortly. Once it's taggedlatest, that range will accept it, sonpm installwill pair these Solid 1 adapters with Solid 2 without any peer warning, and they will fail at build or run time: Solid 2 removessolid-js/store,createComputed,mergeProps/splitProps,onMount,batchand more.This PR changes each range from
>=Xto^X, keeping the same lower bound, and adds a patch changeset so the cap actually ships. Solid 2 support can then come as a new adapter major on a pre-release branch, the way@tanstack/solid-router2.x and@tanstack/solid-query6.x did it.Prereleases (
2.0.0-rc.*) never matched>=1.x, which is why nobody has run into this yet.✅ Checklist
peerDependenciesranges and a changeset change; no code changes.Summary by CodeRabbit