diff --git a/CHANGELOG.md b/CHANGELOG.md index 763ca67..b5fc99f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,10 +4,6 @@ All notable changes to `@ichava/js-icon-components` follow [Keep a Changelog](ht ## [Unreleased] -### Changed - -- The SVG policy interpreter (`src/generator/svgPolicy.ts`) is pinned to `ichava/icon-browser`'s `resources/js/modules/svg/domain/svgPolicy.ts`, not to the retired react-icon-browser, so `tests/vendored.test.ts` compares it with the live copy. Its body and digest are unchanged. - ## [0.1.0] - 2026-11-13 First release. @@ -30,6 +26,8 @@ First release. ### Changed +- The SVG policy interpreter (`src/generator/svgPolicy.ts`) is pinned to `ichava/icon-browser`'s `resources/js/modules/svg/domain/svgPolicy.ts`, not to the retired react-icon-browser, so `tests/vendored.test.ts` compares it with the live copy. Its body and digest are unchanged. + - **The install docs offer both paths in order.** The README's Install and `docs/installation.md` lead with the release tarball (`npm install` of the release URL, and the `SHA256SUMS` check), for an install with no build, then the git install, for contributors or a pinned commit. The git install itself is unchanged. - **The install docs name the real `v0.1.0` release.** `docs/installation.md` opens with a choice between the tarball and the git build, gives the full and per-pack tarball URLs, shows how to check one against `SHA256SUMS`, and pins git installs to `#v0.1.0`; the README's Install section follows. Both said there was no release yet.