Repository navigation
Version Packages - #896
Open
github-actions[bot] wants to merge 1 commit into
Open
Version Packages#896github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
|
This pull request was not reviewed automatically because it was opened by a bot. A maintainer with write access can start a review by commenting |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
October 28, 2026 15:29
42a9c1b to
d0b88e3
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 28, 2026 23:47
d0b88e3 to
a0ef8f2
Compare
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
@cloudflare/kumo@2.17.0
Minor Changes
maskedoption toClipboardTextfor sensitive values that should be hidden initially and revealed on demand.Patch Changes
Fieldno longer renders a<label>when it would be empty: whenlabelandlabelTooltipare eachundefined,null, a boolean or"", and there is no "(optional)" indicator. This fixesInput,InputAreaandTagInputwithout alabelbut with a description or error: they no longer show an empty row above the control, and theiraria-labelis no longer replaced by an empty accessible name.LayerDialog.Separatorfor dividing sections of dialog body content.Tooltipnow keeps its own trigger out of the tab order while the tooltip isdisabled. This applies only when Kumo renders the trigger (norenderorasChild), for example around truncatedTextthat needs a tooltip only when it overflows. A disabled tooltip there has nothing to reveal, so keyboard users no longer stop on it. Custom triggers passed throughrenderkeep their own focus behavior.@cloudflare/kumo-docs-astro@1.5.25
Patch Changes
@cloudflare/kumo-figma@0.3.55
Patch Changes