Repository navigation
chore(release): version packages - #127
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
October 16, 2026 14:44
ce3c37a to
81dd88d
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 16, 2026 14:48
81dd88d to
2127e81
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
@shadcn/lint@0.2.3
Patch Changes
#122
cf6487fThanks @shadcn! - Accept--border-color-*tokens fordivide-*inno-raw-colors, the way Tailwind falls back from--divide-color-*.#107
f1c81bdThanks @shadcn! - Check a component reached through a nested namespace,<UI.Button.Root>, resolving each segment throughexport * asbarrels.#126
cbc8d4dThanks @shadcn! - Classify tw-animate-css classes such asanimate-in,fade-in, andslide-in-from-top-1asmotioninno-restylewhen the theme imports the package.#121
24a73eeThanks @shadcn! - Resolve theme variables such as--radiusfrom:rootand@themefor scale and color suggestions, not from a scoped selector such as.compactdeclared after them.#123
c0d164bThanks @shadcn! - Skip plain object property keys such as"fill-color"in thescanAllStringsscan. Class object keys likecn({ "bg-red-500": on })are still checked.#106
355eb51Thanks @shadcn! - Check a CSS custom property passed to a Svelte component,<Button --tone="red">, the wayno-inline-styleschecks it in astyleattribute.#104
acee889Thanks @shadcn! - Resolve a Svelte$derived(expr)binding toexpr, so reactive class and style values are read like aconst.#105
808970eThanks @shadcn! - Checkstop-color,flood-color, andlighting-colorin Svelte and Vue markup the wayno-raw-colorschecksstopColorin JSX.#124
118a109Thanks @shadcn! - Accept a color function whose channels are one theme variable, such asoklch(var(--primary-oklch) / 0.2), inno-raw-colorsSVG attributes andno-inline-stylescustom properties. Literal channels and avar()fallback are still reported.#125
1d31b7fThanks @shadcn! - Check a wrapper's other class props, such asheaderClassName, inno-restyleagainst the component the wrapper hands them to, not the one that receivesclassName.