Skip to content

Version Packages #438

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Version Packages #438

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 0 additions & 13 deletions .changeset/navigate-re-export.md
View file
Open in desktop

This file was deleted.

19 changes: 0 additions & 19 deletions .changeset/olive-donkeys-shake.md
View file
Open in desktop

This file was deleted.

9 changes: 0 additions & 9 deletions .changeset/wild-moons-repeat.md
View file
Open in desktop

This file was deleted.

38 changes: 38 additions & 0 deletions packages/core/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,43 @@
# @tailor-platform/app-shell

## 1.12.0

### Minor Changes

- b5289fc: Re-export react-router's `Navigate`, so apps no longer need `react-router` as a direct dependency for declarative redirects.

```tsx
import { Navigate } from "@tailor-platform/app-shell";

if (!allowed) return <Navigate to="/dashboard" replace />;
```

See [Declarative Redirects](https://github.com/tailor-platform/app-shell/blob/main/docs/concepts/routing-navigation.md#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:

```tsx
// Before — arbitrary values, no autocomplete, silent failure on a typo
<div className="bg-[color:var(--alert-info-background)] text-[color:var(--alert-info-foreground)]" />

// After
<div className="bg-alert-info-background text-alert-info-foreground" />
```

This is purely additive — existing arbitrary-value usage keeps working, and the generated CSS is unchanged.

### Patch Changes

- 45218cc: Fix the bundled `app-shell-patterns` skill, whose `design-system.md` documented a token system that does not exist in the package. Agents read it as canonical and emitted classes like `bg-surface-1`, `text-fg-default`, and `bg-danger`, which produce no CSS at all — a silent failure with no error or warning.

Tokens, dark mode (`.dark` on `<html>`), elevation, z-index, and the `styles` import now match the shipped CSS, and the fabricated spacing, typography, motion, and icon scales are gone in favour of stock Tailwind. Also drops references to `Icon` and `Stat`, which aren't exported, and to a `Sheet` `contentClassName` prop that doesn't exist.

Documentation only — no runtime or CSS changes.

## 1.11.0

### Minor Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/core/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@tailor-platform/app-shell",
"version": "1.11.0",
"version": "1.12.0",
"description": "An opinionated React application framework for building ERP applications on Tailor Platform",
"keywords": [
"app-shell",
Expand Down