Version Packages - #1371
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
🧪 Storybook is successfully deployed!
|
Contributor
🏋️ Size limit report
Compared against main at 154a701 — run 33065369602, 2026-08-27T10:59:03Z.To see which modules changed, download the size-limit-statoscope-report artifact from this run and open report.html. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 main, this PR will be updated.
Releases
@cube-dev/ui-kit@0.171.0
Minor Changes
#1370
154a701fThanks @tenphi! -<Board collisionMode="swap">now places a widget arriving from another board instead of cancelling the transfer.swapused to treat a cross-board arrival as strict insertion: the anchor cell had to be empty, and releasing over an occupied one cancelled the whole transfer — both boards snapped back andonWidgetTransfernever fired. That made the mode's two halves unusable together, since a board that wanted in-board swapping had to give up cross-board drops (or pickdownscaleand give up the swap).A cross-board arrival now resolves the same way
downscaledoes: it keeps its size where the drop cell allows, downscales into the room to its right and below where it does not, and holds the last cell it fitted in as the pointer sweeps across a destination widget — so releasing over an occupied cell commits what the preview was showing. Entering a board directly over an occupied cell places the widget in the nearest cell that fits. Destination widgets are still never exchanged, pushed, or reflowed to make space — only the arrival moves. In-board drops are unchanged and still swap.Also fixes a cross-board landing under any
collisionModewhere a refused placement committed the widget one row above the board (y: -1) instead of on it.Patch Changes
#1370
154a701fThanks @tenphi! -<Board collisionMode="downscale">(and the cross-board half of"swap") now shrinks a widget into free room on either side of a blocker, not just the left.gridBoundsclamps a drag anchor tocols - w, which assumes the widget keeps the width it started with. So when the blocker sat to the left and the room to its right was narrower than the widget, every anchor a pointer could produce landed inside the blocker — the mode whose whole job is to shrink the widget into that room never got offered it, and the drop just reverted. Dropping into room on the left always worked, because column 0 is reachable whatever the widget's width.A blocked drop whose anchor is pinned against the grid edge now also considers the cells beyond it that the clamp hid, taking the largest fit among them. An anchor short of the limit is the pointer's own choice — every cell between it and the limit was available to aim at — so a blocked drop there still reverts, and every drop that resolved before resolves to exactly the same cell. The row axis clamps the same way, so boards with a finite
maxRowsget the same fix below a blocker.Note
Low Risk
This diff only versions and documents the release; runtime risk comes from the already-merged Board collision changes affecting grid drag-and-drop UX, not from security or data paths.
Overview
Release packaging for
@cube-dev/ui-kit0.171.0: bumpspackage.json, appends 0.171.0 toCHANGELOG.md, and removes the consumed changeset entries.The release notes capture Board drag/drop behavior from #1370:
collisionMode="swap"now places cross-board arrivals (downscale-style fitting and preview commit) instead of cancelling transfers and blockingonWidgetTransfer;downscale(and swap’s cross-board path) can shrink into free space on either side of a blocker when the anchor is edge-clamped bygridBounds; and refused cross-board placements no longer land aty: -1.Reviewed by Cursor Bugbot for commit b25dc3f. Bugbot is set up for automated code reviews on this repo. Configure here.