Repository navigation
chore(release): version packages - #1
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 9, 2026 12:50
21d4fde to
11ad0a8
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 9, 2026 14:14
11ad0a8 to
7fe50e4
Compare
edwintantawi
added a commit
that referenced
this pull request
Sep 9, 2026
`changeset status --since=origin/main` needs a merge base, and `actions/checkout` clones one commit deep by default: the ref does not exist on the runner and neither does the history behind it. The step failed on the first PR to reach it - PR #1 was the release PR, which the `if:` skips - with "Failed to find where HEAD diverged from origin/main". release.yml already asks for `fetch-depth: 0` for the same reason. This is the copy of that line ci.yml should have had.
edwintantawi
added a commit
that referenced
this pull request
Sep 9, 2026
* feat(core): add the Accordion component
A stack of disclosure rows in the same token-driven shape as the rest of the
set. `contained` groups the rows on one surface and divides them; `separated`
gives each its own outline. `exclusive` opens one row at a time, and a row can
be disabled.
Underneath it is `<details>` and `<summary>`, so the keyboard, the screen reader
and find-in-page behaviour are the platform's rather than ours - and `exclusive`
is nothing but the shared `name` attribute, so no state tracks which row is
open.
Four decisions worth writing down:
- Rows arrive as an `items` array rather than as children. A compound
`<Accordion.Item>` would have to read the group's variant and its `exclusive`
group name out of React context on every render, and the package README
advertises that nothing here does a context lookup in the render path. That
paragraph is extended rather than quietly falsified.
- The chevron mirrors the element's own open state through `onToggle` instead of
turning in CSS. `stylex.when.ancestor('[open]')` compiles to
`:where(.marker[open] *)`, which reaches every chevron under an open row and
would rotate the closed ones of a nested Accordion with it.
- `contained` draws its dividers by painting the group in the border token and
letting a `gap` of the same width show through between opaque rows. No
`:first-child` rule to exempt the first one, and a theme that thickens its
outlines thickens the dividers to match.
- A disabled row takes the pointer away from its summary and drops it out of the
tab order rather than cancelling the click. Enter on a focused summary *is* a
click, so both routes had to go; the `not-allowed` cursor sits on the row,
since a summary that ignores the pointer cannot set one.
The example app gains an Accordion section showing both variants, the exclusive
group and the disabled row.
* ci: give the changeset gate the history it diffs against
`changeset status --since=origin/main` needs a merge base, and
`actions/checkout` clones one commit deep by default: the ref does not exist on
the runner and neither does the history behind it. The step failed on the first
PR to reach it - PR #1 was the release PR, which the `if:` skips - with "Failed
to find where HEAD diverged from origin/main".
release.yml already asks for `fetch-depth: 0` for the same reason. This is the
copy of that line ci.yml should have had.
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
@batik-prototype/core@0.1.0
Minor Changes
3f8e8b6Thanks @edwintantawi! - Add the design system:Button,Input,CardandBadge, the design token contractthey read from, and the React runtime that applies a theme.
Tokens are StyleX variable groups, published one
.stylexentry point per concern, so atheme package can override them by name.
ThemeProviderapplies a theme to a subtree andresolves
'system'against the OS;defineThemeandresolveThemeare the React-freeauthoring contract, also available at
@batik-prototype/core/theme.The variable defaults are the Classic light palette, so an app that installs nothing else
already renders a finished-looking UI.
@batik-prototype/theme-classic@0.1.0
Minor Changes
009ec49Thanks @edwintantawi! - Add the first three Batik themes, each a package of its own.Classic is the default and supplies only a dark scheme, since the token defaults in
@batik-prototype/corealready are its light palette. Ocean overrides colour, shadow andradius; Sunset overrides colour, shadow, radius and type, to show that a theme's reach is
not limited to colour.
Patch Changes
3f8e8b6]:@batik-prototype/theme-ocean@0.1.0
Minor Changes
009ec49Thanks @edwintantawi! - Add the first three Batik themes, each a package of its own.Classic is the default and supplies only a dark scheme, since the token defaults in
@batik-prototype/corealready are its light palette. Ocean overrides colour, shadow andradius; Sunset overrides colour, shadow, radius and type, to show that a theme's reach is
not limited to colour.
Patch Changes
3f8e8b6]:@batik-prototype/theme-sunset@0.1.0
Minor Changes
009ec49Thanks @edwintantawi! - Add the first three Batik themes, each a package of its own.Classic is the default and supplies only a dark scheme, since the token defaults in
@batik-prototype/corealready are its light palette. Ocean overrides colour, shadow andradius; Sunset overrides colour, shadow, radius and type, to show that a theme's reach is
not limited to colour.
Patch Changes
3f8e8b6]: