Skip to content

Version Packages (next)#859

Open
github-actions[bot] wants to merge 1 commit intonextfrom
changeset-release/next
Open

Version Packages (next)#859
github-actions[bot] wants to merge 1 commit intonextfrom
changeset-release/next

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 1, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

layerchart@2.0.0-next.63

Patch Changes

  • fix(Chart): Don't compute [undefined, undefined] domain when series is metadata-only (#449)

    When series is configured for legend/color metadata only (no per-series data, and items lack the series-key properties on the value axis), the value-axis domain calculation collected all-undefined values and returned [undefined, undefined]. Combined with motion, this threw Cannot spring undefined values whenever the series visibility changed (e.g. toggling a legend swatch).

    The series-aware branch now filters out null/undefined values and falls through to the other domain-resolution paths when nothing remains, instead of returning a poisoned extent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants