From 0eceedd6fd2aa571f7fe96d395bce7c52d43674f Mon Sep 17 00:00:00 2001 From: Imani Manyara Date: Fri, 13 Nov 2026 16:02:02 -0500 Subject: [PATCH] File the remaining unreleased notes under 0.1.0 --- CHANGELOG.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c5af433..30b0b81 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,20 +4,14 @@ All notable changes to `@ichava/js-icon-components` follow [Keep a Changelog](ht ## [Unreleased] -### Added - -- **The release checks its tarball against the install URL.** `scripts/check-release-name.mjs` runs in `release.yml` after packing and before publishing, and fails unless the release directory holds the full tarball under the exact name `tarballUrl()` in `scripts/prepare.mjs` gives for the tag (the command an `"install": "tarball"` refusal prints) and `SHA256SUMS` lists it. Pre-release tags are checked the same way. `tests/release-name.test.ts` covers final and pre-release tags, a drifted name and the workflow step's place (proven red by renaming the file in `tarballUrl()`, and by removing the step). - -### Changed - -- **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. - ## [0.1.0] - 2026-11-13 First release. ### Added +- **The release checks its tarball against the install URL.** `scripts/check-release-name.mjs` runs in `release.yml` after packing and before publishing, and fails unless the release directory holds the full tarball under the exact name `tarballUrl()` in `scripts/prepare.mjs` gives for the tag (the command an `"install": "tarball"` refusal prints) and `SHA256SUMS` lists it. Pre-release tags are checked the same way. `tests/release-name.test.ts` covers final and pre-release tags, a drifted name and the workflow step's place (proven red by renaming the file in `tarballUrl()`, and by removing the step). + - **`"ichava": { "icons": { "install": "tarball" | "build" } }`**, also `ICHAVA_ICONS_INSTALL`, makes the install path a setting. `tarball` stops a git install and prints the release tarball command for this version; `build`, or no key, is today's git build; any other value fails the install, listing the two. A built `dist/` is never refused, so the tarball itself installs as before. `tests/prepare.test.ts` covers each value (proven red by disabling the refusal). - **Three Tier 3 flavours** (icon-browser schema 1.6.0, now 1.8.0, vendored with its digest): Qwik (`./qwik`, one lightweight component per icon; Qwik's server renderer and optimizer in the test), Ember (`./ember`, a template-only Glimmer component in template-tag format, compiled with content-tag and checked by the Glimmer precompiler) and Elm (`dist/elm/Ichava/Icons/.elm`, one `Svg msg` function per icon, compiled with `elm make` from npm's `elm` package and run in jsdom in the test). `@builder.io/qwik` and `ember-source` are optional peers. - **Four asset exports** under `dist/assets//`, chosen in the same `ICHAVA_ICONS_FLAVOURS` list as the flavours: `icons.css` (CSS mask, one `.i--` class per icon), `data-uri.json` (percent-encoded SVG data URIs), `flutter.zip` (SVG assets, Dart path constants and a `pubspec` fragment for `flutter_svg`) and `swiftui.zip` (an `.xcassets` catalog, `template` rendering for one-colour icons, `original` otherwise). All four carry SVG: the ichava icon ecosystem is strictly SVG. Every export is written from the parsed, policy-checked tree, carries the pack's attribution, and is counted from its files by the count guard. @@ -32,6 +26,8 @@ First release. ### Changed +- **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. - **Every pin names its source's v0.1.0 root** for the re-squash, which gives each repository one root commit with the tree of its `main`: the packs at tabler `eddbd69f`, flag `5acfe40c`, twemoji `b0d686fb` and openmoji `4c06bb6e` (each on GitHub now as branch `release/v0.1.0-root`, so the build's shallow fetch works before and after the squash), and `vendor/source.json` at core `9bd8b3a9`, icon-browser `97631b19` and react-icon-browser `054c2b32`. The trees hold the same SVGs as the previous pins; the copies' digests are unchanged. - **The vendored SVG policy and icon-browser schema name their sources' v0.1.0 roots**: core `c2d79a6b` and icon-browser `466b8fb1`, the root commits the re-squash cuts from today's `main` of each. Both files are byte-identical at those trees (SHA-256 unchanged).