AlgoScan

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

The standalone (non-Tailwind) CSS ships a minimal scoped reset instead of
Tailwind's full preflight. It mirrored preflight for <img> but omitted the
<svg> rule, so library icons fell back to the UA default display: inline.
The inline baseline gap distorted tightly-wrapped controls such as the
rounded "Close dialog" button. The Tailwind flavor was unaffected because
the consumer's own preflight already sets svg { display: block }.

Add a scoped svg reset (display: block; vertical-align: middle) mirroring
preflight and the existing img reset, fixing all library icons in the
standalone flavor without affecting consumer elements.

The standalone (non-Tailwind) CSS ships a minimal scoped reset instead of
Tailwind's full preflight. It mirrored preflight for <img> but omitted the
<svg> rule, so library icons fell back to the UA default display: inline.
The inline baseline gap distorted tightly-wrapped controls such as the
rounded "Close dialog" button. The Tailwind flavor was unaffected because
the consumer's own preflight already sets svg { display: block }.

Add a scoped svg reset (display: block; vertical-align: middle) mirroring
preflight and the existing img reset, fixing all library icons in the
standalone flavor without affecting consumer elements.

Made-with: Cursor

* ci: gate React release on releasable React commits, not file changes

The previous guard watched file paths including the shared pnpm-lock.yaml,
so any Vue change that regenerated the lockfile tripped it. It also only
checked whether files changed, not whether a releasing commit touched the
React package — so accumulated chore(deps) bumps plus a Vue feat commit
still cut a React release (react@1.2.0 from the #55 merge).

Gate instead on whether a feat/fix/BREAKING commit since the last v* tag
actually touched packages/react (git log pathspec excludes Vue-only commits;
the type check ignores chore-only ranges).

Uses a ci: type so semantic-release will not release this change even if the
guard runs.

* docs(changelog): clarify react@1.2.0 contained only dependency updates

The 1.2.0 entry was auto-generated as a 'feat: add Vue library' minor bump,
but the React package had no functional changes — 1.2.0 only bundles the
dependency updates accumulated since 1.1.0. Reword the entry to reflect that
and reference the guard fix (#70).

The 1.2.0 entry was auto-generated as a 'feat: add Vue library' minor bump,
but the React package had no functional changes — 1.2.0 only bundles the
dependency updates accumulated since 1.1.0. Reword the entry to reflect that
and reference the guard fix (#70).

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

The previous guard watched file paths including the shared pnpm-lock.yaml,
so any Vue change that regenerated the lockfile tripped it. It also only
checked whether files changed, not whether a releasing commit touched the
React package — so accumulated chore(deps) bumps plus a Vue feat commit
still cut a React release (react@1.2.0 from the #55 merge).

Gate instead on whether a feat/fix/BREAKING commit since the last v* tag
actually touched packages/react (git log pathspec excludes Vue-only commits;
the type check ignores chore-only ranges).

Uses a ci: type so semantic-release will not release this change even if the
guard runs.

# [1.2.0](https://github.com/TxnLab/use-wallet-ui/compare/v1.1.0...v1.2.0) (2026-06-08)

### Features

* add Vue library ([#55](https://github.com/TxnLab/use-wallet-ui/issues/55)) ([4d10cdd](https://github.com/TxnLab/use-wallet-ui/commit/4d10cdd38faec2ea03f6877ad50fcd620582ed19))