Skip to content

An open source design system that's fully customizable and agent ready

TypeScript

chore(changesets): cite introducing changes and final-state evidence (#7923)

Cindy Zhangcac3d8dca37d
diff --git a/.changeset/build-search-routing.md b/.changeset/build-search-routing.md
index 07f0ca5c79..e69f94ff7b 100644
--- a/.changeset/build-search-routing.md
+++ b/.changeset/build-search-routing.md
@@ -2,7 +2,7 @@
'@astryxdesign/cli': patch
---
-[feat] `astryx search` orders the matches inside each score band so the entry you are after comes first more often; every result keeps its match score and reason, and a query that is an entry's exact name still answers with that entry first.
+[feat] `astryx search` orders the matches inside each score band so the entry you are after comes first more often; every result keeps its match score and reason, and a query that is an entry's exact name still answers with that entry first. Introduced in [#7752](https://github.com/facebook/astryx/pull/7752); final-state evidence: [#7895](https://github.com/facebook/astryx/pull/7895) and [#7897](https://github.com/facebook/astryx/pull/7897).
`astryx build` names the right block first more often; its page call, start template, and alternatives are unchanged.
@josephfarina
diff --git a/.changeset/date-range-input-focusable-disabled.md b/.changeset/date-range-input-focusable-disabled.md
index 55d4bea3bb..204b8b2aef 100644
--- a/.changeset/date-range-input-focusable-disabled.md
+++ b/.changeset/date-range-input-focusable-disabled.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] DateRangeInput: a disabled or busy field and a disabled preset no longer render native `disabled`. The trigger, calendar button and presets keep their place in the focus order and expose `aria-disabled`, while opening and selecting stay blocked, and a focused disabled field shows its focus ring. This meets the focusable-disabled requirement in spec:AST-085 (FR1, FR2, FR6) and DateRangeInput AR3. Tests that query them with `toBeDisabled()` or `:disabled` should check `aria-disabled="true"` instead.
+[fix] DateRangeInput: a disabled or busy field and a disabled preset no longer render native `disabled`. The trigger, calendar button and presets keep their place in the focus order and expose `aria-disabled`, while opening and selecting stay blocked, and a focused disabled field shows its focus ring. This meets the focusable-disabled requirement in spec:AST-085 (FR1, FR2, FR6) and DateRangeInput AR3. Tests that query them with `toBeDisabled()` or `:disabled` should check `aria-disabled="true"` instead. Introduced in [#7866](https://github.com/facebook/astryx/pull/7866); final-state evidence: [#7887](https://github.com/facebook/astryx/pull/7887).
@cixzhang
diff --git a/.changeset/init-agent-docs-one-copy.md b/.changeset/init-agent-docs-one-copy.md
index 6ed9cf2da2..1aed82f2fe 100644
--- a/.changeset/init-agent-docs-one-copy.md
+++ b/.changeset/init-agent-docs-one-copy.md
@@ -3,7 +3,7 @@
'@astryxdesign/core': patch
---
-[fix] `astryx init` writes the agent docs at the project root, in files the project commits, so that Codex, Gemini CLI, Copilot CLI and Claude Code all read the block, from the project root or any folder below it. It no longer writes agent docs into a project's subfolder, the home folder, or a settings folder in it such as `~/.gemini`.
+[fix] `astryx init` writes the agent docs at the project root, in files the project commits, so that Codex, Gemini CLI, Copilot CLI and Claude Code all read the block, from the project root or any folder below it. It no longer writes agent docs into a project's subfolder, the home folder, or a settings folder in it such as `~/.gemini`. Introduced in [#7497](https://github.com/facebook/astryx/pull/7497); final-state evidence: [#7888](https://github.com/facebook/astryx/pull/7888).
@josephfarina
- `AGENTS.md` holds the block, created when missing. Before, a project with only `CLAUDE.md` got the block only there, so Codex and Gemini CLI never saw it.
diff --git a/.changeset/search-reuses-gathered-catalog.md b/.changeset/search-reuses-gathered-catalog.md
index 5ce101d55b..f2c6b62b6c 100644
--- a/.changeset/search-reuses-gathered-catalog.md
+++ b/.changeset/search-reuses-gathered-catalog.md
@@ -2,6 +2,6 @@
'@astryxdesign/cli': patch
---
-[fix] `search()` from `@astryxdesign/cli/api` answers faster when one process searches again: it reuses the components, docs, templates and themes it gathered for the same folder and `type` while no file it read, and no folder it listed, has changed since (a linked workspace package included). To see those reads, the first such search in a process wraps `node:fs`'s read functions for that process; outside a search they behave exactly as before. Results are unchanged. Short-lived runs are unaffected: each `astryx search` command gathers once, as before.
+[fix] `search()` from `@astryxdesign/cli/api` answers faster when one process searches again: it reuses the components, docs, templates and themes it gathered for the same folder and `type` while no file it read, and no folder it listed, has changed since (a linked workspace package included). To see those reads, the first such search in a process wraps `node:fs`'s read functions for that process; outside a search they behave exactly as before. Results are unchanged. Short-lived runs are unaffected: each `astryx search` command gathers once, as before. Introduced in [#7830](https://github.com/facebook/astryx/pull/7830); final-state evidence: [#7885](https://github.com/facebook/astryx/pull/7885).
@josephfarina
diff --git a/.changeset/timestamp-server-clock.md b/.changeset/timestamp-server-clock.md
index 257ca58b93..c4e585a232 100644
--- a/.changeset/timestamp-server-clock.md
+++ b/.changeset/timestamp-server-clock.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Timestamp no longer reads the current time while rendering on the server. Absolute formats (`date`, `time`, `date_time` and the other fixed formats) never read the clock, so pages that use them prerender in Next.js with `cacheComponents` turned on, the default for new Next.js 16 apps, where they used to fail the build. `relative`, `relative_short` and `auto` read the clock on the client only: a server render or static prerender shows the full date and time in UTC, labelled, and the client switches to the format's normal output right after hydration, so server and client markup now always match. Client-only rendering is unchanged. No API changes.
+[fix] Timestamp no longer reads the current time while rendering on the server. Absolute formats (`date`, `time`, `date_time` and the other fixed formats) never read the clock, so pages that use them prerender in Next.js with `cacheComponents` turned on, the default for new Next.js 16 apps, where they used to fail the build. `relative`, `relative_short` and `auto` read the clock on the client only: a server render or static prerender shows the full date and time in UTC, labelled, and the client switches to the format's normal output right after hydration, so server and client markup now always match. Client-only rendering is unchanged. No API changes. Introduced in [#7883](https://github.com/facebook/astryx/pull/7883); current release evidence: [#7921](https://github.com/facebook/astryx/pull/7921), not the Timestamp implementation.
@josephfarina