chore: release packages production - #142
Merged
Merged
Conversation
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
@indielayer/ui@2.0.0
Major Changes
Migrate to Tailwind CSS v4 with a CSS-first public API.
Breaking changes
tailwindcss@^4.0.0(requires Safari 16.4+, Chrome 111+, Firefox 128+).@indielayer/ui/tailwind.preset— use@import "@indielayer/ui/tailwind.css"in your app stylesheet instead.@sourcedirectives; JavaScripttailwind.config.jspresets are no longer used.Migration
@tailwindcss/postcss(Vite:css.postcss.plugins; Nuxt:postcss.plugins).@tailwinddirectives with@import "tailwindcss"and import@indielayer/ui/tailwind.css.@sourcepaths includingnode_modules/@indielayer/ui/{lib,src}/**/*.shadow-sm→shadow-xs,flex-grow→grow,outline-none→outline-hidden, etc.) if you copied v3 class names.See the Tailwind upgrade guide and the docs getting-started page.
(#139) (
8744d9d)Minor Changes
feat(table): optional multiple sort (#139) (
8744d9d)Add
defaultsoption onUIOptionsfor app-wide component prop defaults (e.g.Alert: { outlined: true }). Defaults merge inuseThemeand viauseResolvedComponentPropsfor template usage. Themed components useoptionalBooleanProp()for variant/layout booleans so omitted props stayundefinedand receive app defaults (Vue otherwise coerces plainBooleantofalse). (#139) (8744d9d)Add
XEmptycomponent for empty states with title, description, icon, actions slot, and optional bordered layout. (#139) (8744d9d)Add
XInputGroupfor inline multi-field controls with a shared label and InputFooter. SupportsXInput,XTextarea,XSelect, andXDatepickeras children. (#139) (8744d9d)feat(stepper)!: rebuild as multi-step wizard with named slots and navigation API
BREAKING CHANGE:
XStepperno longer uses manualstatusorlabelon steps. Usevalue,title, named panel slots (#stepId), optional#summary-stepIdslots, and exposednext()/prev()/goTo()/reset()methods.v-modelis the active stepvalue(string or number), not a numeric index.(#139) (
8744d9d)