Version Packages - #438
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
August 13, 2026 03:20
ecaa15e to
3e1f563
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 04:21
3e1f563 to
793ff24
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
@tailor-platform/app-shell@1.12.0
Minor Changes
b5289fc: Re-export react-router's
Navigate, so apps no longer needreact-routeras a direct dependency for declarative redirects.See Declarative Redirects for when to prefer the route-level
redirectTo()guard instead.fa587b2: Bridge
--alert-*tokens into Tailwind's theme as--color-alert-*The
--alert-*design tokens (neutral/success/warning/error/info×background/foreground/foreground-muted/border) are now exposed through@theme inline, matching how--status-*is already bridged.Application code can now use ordinary color utilities for callouts, banners, and status-highlighted rows:
This is purely additive — existing arbitrary-value usage keeps working, and the generated CSS is unchanged.
Patch Changes
45218cc: Fix the bundled
app-shell-patternsskill, whosedesign-system.mddocumented a token system that does not exist in the package. Agents read it as canonical and emitted classes likebg-surface-1,text-fg-default, andbg-danger, which produce no CSS at all — a silent failure with no error or warning.Tokens, dark mode (
.darkon<html>), elevation, z-index, and thestylesimport now match the shipped CSS, and the fabricated spacing, typography, motion, and icon scales are gone in favour of stock Tailwind. Also drops references toIconandStat, which aren't exported, and to aSheetcontentClassNameprop that doesn't exist.Documentation only — no runtime or CSS changes.