Skip to content

chore(release)!: prepare UI 0.0.3 with core 0.3.4 - #170

Merged
elonehoo merged 2 commits into
mainfrom
release/ui-0.0.3
Nov 5, 2026
Merged

elonehoo merged 2 commits into
mainfrom
release/ui-0.0.3

Conversation

@elonehoo

@elonehoo elonehoo commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Synchronize the root and four public UI packages at 0.0.3.
  • Raise all 59 core catalog ranges to ^0.3.4, resolve the 73-package core dependency closure to the actual published 0.3.4 artifacts, and pin the exact-core consumer gate to 0.3.4.
  • Add release and migration guidance. Runtime code and existing test assertions from fix(vue): preserve Steps and Select caller events #169 are unchanged; existing test edits only remove stale version-specific comments and a describe label.
  • Add a small, UI0.0.3-scoped changelogithub configuration and an explicit actual-generator render test. The generated release body includes the breaking migrations and retained Vue listener limit without editing workflows or requiring a release-body edit from the tag-only Mac task.

Breaking migrations and known limits

Core 0.3.4 was explicitly selected despite compatibility changes. Steps now uses one roving tab stop, arrow/Home/End focus navigation and a completion summary without an invalid tabpanel role. Default composite Select focus belongs to Content rather than a nested List tab stop. Patch version numbers do not remove the need to migrate.

UI0.0.3 migration notes include immutable core migration links, supported trigger composition and upgrade instructions. The range ^0.0.2 excludes UI0.0.3; core ^0.3.3 already admits 0.3.4 on fresh resolution.

The existing Vue wrapper option-suffixed .once.prevent ordering limitation remains: a core action may run before the once handler. Capture/passive behavior is unchanged; this is not a universal focus/pointer cancellation contract.

Verification

  • Core0.3.4 release run 42040791589, attempt1 succeeded at commit16e22b9336e18b6026aa7f0049a2470ffe65392b.
  • All76 core registry artifacts passed independent manifests, integrity and source/tag/run provenance binding checks, plus separate cryptographic Sigstore verification.
  • Every UI core lock integrity matches those verified artifacts. Independent whole-lock comparison confirms only intended core version/integrity changes across catalogs, importers, packages and snapshots; 1,518 non-core package entries are unchanged.
  • Frozen install with pnpm10.28.0 passed. Native script tests:406 passed. All four frameworks' unit/SSR projects:1,118 tests in97 files passed. All framework typechecks passed. ESLint:0 errors,667 existing warnings.
  • An initial parallel local attempt was externally resource-terminated without assertion diagnostics; serial reruns above passed. Those logs are retained. All four framework build/pack/exact-core installed-consumer checks passed with UI0.0.3 and actual core0.3.4. Each consumer's69 resolved core integrities also match the independent published-artifact evidence.
  • The initial17-file candidate at16c5625 passed all seven repository workflows and automated reviews. The final19-file candidate at6678d1d adds only the reviewed config/test/documentation follow-on, and full CI is running again for that exact head.
  • Actual changelogithub15.0.5 config discovery, commit parsing and Markdown rendering passed from both the repository root and /tmp. The explicit manual test verifies tag-pinned migration links, Steps/Select breaking disclosures, the retained.once.prevent limitation and ordinary generated sections; its missing-breaking negative control confirms the final squash must preserve conventional breaking metadata. No publishing CLI/API or contributor lookup ran. This proof is not silently counted as an existing CI test.
  • Normal repository CI must pass for this exact release candidate. Existing prior UI fix(vue): preserve Steps and Select caller events #169 Chromium suites do not replace this new-core verification, and Happy DOM tests are not exhaustive browser or assistive-technology acceptance.

Release gate

This release-preparation PR is ready for review while final-head CI runs. Preserve the squash subject chore(release)!: prepare UI 0.0.3 with core 0.3.4 and its BREAKING CHANGE footer so the generator emits the migration section. Squash merge and a new release are authorized after checks; no formal PR approval is submitted here. A tag will be pushed separately only after the final merged commit, synchronized versions, core identity and all gates are verified. No workflow, peer range, Node floor, shared factory or publication-scope changes are included.


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.


Note

Medium Risk
Synchronized semver and core 0.3.4 adoption affect all frameworks and expose breaking Steps/Select behavior documented for upgrade; release-process risk if squash metadata or generated notes are wrong, not new app logic in this PR.

Overview
Prepares UI 0.0.3 by bumping the root and all four @destyler-ui/* packages from 0.0.2, raising every workspace @destyler/* catalog entry and pnpm-lock.yaml resolution from ^0.3.3 to ^0.3.4, and pinning pnpm test:core-compat / scripts/test-core-compat.mjs to exact core 0.3.4.

Adds consumer-facing release material: docs/releases/0.0.3.md (Steps keyboard/roles, Select focus ownership, Vue listener ordering limits, upgrade steps), changelogithub.config.mjs scoped to version 0.0.3 so generated GitHub release bodies include migration links when the squash commit is conventional breaking, and scripts/test-release-notes.mjs to render-check changelogithub without network or publish. Release checklists, Vue README, tabs migration docs, and core-compat README are updated to reference 0.0.3 / core 0.3.4; Vue Steps/Select unit tests only drop stale “0.3.3” comments.

No component runtime changes in this diff—the work is version synchronization, dependency closure, and release-note guarantees for core 0.3.4’s accessibility migrations.

Reviewed by Cursor Bugbot for commit 6678d1d. Bugbot is set up for automated code reviews on this repo. Configure here.

Synchronize the four public UI packages, resolve the verified core0.3.4 artifacts and update the exact-core gate. Preserve runtime code and test assertions from #169.

BREAKING CHANGE: Core0.3.4 changes Steps roving Tab order/completion roles and Select default composite focus ownership. Migration notes: https://github.com/destyler/ui/blob/main/docs/releases/0.0.3.md

Existing Vue wrapper .once.prevent cancellation remains limited; capture/passive semantics are unchanged. No publication is performed by this commit.
@vercel

vercel Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
destyler-ui Ready Ready Preview Nov 5, 2026 3:22pm UTC
destyler-ui-dev Ready Ready Preview Nov 5, 2026 3:22pm UTC

@elonehoo
elonehoo marked this pull request as ready for review November 5, 2026 14:53
@elonehoo
elonehoo marked this pull request as draft November 5, 2026 15:07
Use the supported changelogithub breakingChanges title to include tag-pinned UI0.0.3 migrations and retained Vue .once.prevent limits. Scope notices to0.0.3 and retain normal generated sections.

Verify real changelogithub15.0.5 config discovery, parsing and Markdown output without invoking publication. No workflow, dependency, lock or runtime changes.
@elonehoo
elonehoo marked this pull request as ready for review November 5, 2026 15:14
@elonehoo
elonehoo merged commit dfccf73 into main Nov 5, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant