Skip to content

Sanchika v0.1.1

Latest

Choose a tag to compare

@lamemustafa lamemustafa released this 16 Jul 12:14
f5f86ea

Sanchika v0.1.1

Summary

Sanchika v0.1.1 is a release-engineering correction to the v0.1.0
three-package GitHub artifact release. It preserves the reviewed v0.1.0
package contracts while making stable tarball bytes reproducible between the
release checkout and the Pages release-evidence gate.

The v0.1.0 tag and assets remain immutable. This correction does not replace
them, publish to npm, or add package APIs, tokens, primitives, patterns,
motion contracts, gallery features, or consumer changes.

Release Set

  • @sanchika/tokens@0.1.1
  • @sanchika/primitives@0.1.1
  • @sanchika/patterns@0.1.1

The release distributes GitHub tarball assets. It does not publish packages to
npm. The private gallery application is deployed separately and is not packed.

Correction Since v0.1.0

  • Stable artifact generation now rejects any runtime other than Node
    24.18.0, npm 11.16.0, and zlib 1.3.1-e00f703 before building or emitting a
    release directory.
  • CI and Pages use the exact Node version in .node-version.
  • The stable pack path repeats the runtime assertion when invoked directly.
  • Ordinary gallery builds retain v0.1.0 as current and expose v0.1.1 as the
    candidate; the stable release runner promotes v0.1.1 only for evidence that
    the Pages published-release gate must verify before deployment.
  • Release, manifest, checksum, install, migration, and public status metadata
    advance together to v0.1.1.

The correction is necessary because npm produced byte-identical uncompressed
tar payloads but different gzip bytes under different Node-bundled zlib
versions. Checksums still derive from final .tgz bytes; the release gate is
not weakened to compare only decompressed content.

Compatibility

  • Existing v0.0.2 token CSS aliases remain available for the documented
    compatibility window.
  • Legacy TypeScript token collections remain supported.
  • The PrimitiveSpec compatibility shape remains supported.
  • The Button, Card, Badge, and Field registry prefix and valid legacy
    class output remain unchanged.
  • Existing legacy pattern exports remain supported, including the retained
    patternSpecs shape and approved alias behavior.
  • There is no intentional JavaScript, declaration, CSS, export, or runtime
    behavior change from v0.1.0 at the three stable package entrypoints.
  • Packed manifests advance the package and exact internal dependency versions
    together to 0.1.1; packed READMEs advance their GitHub install URLs and
    version explanations to v0.1.1.
  • APIs remain pre-1.0 and experimental; consumers must verify their own
    composed runtime and accessibility behavior.

Known Limitations

  • Packages are not published to npm.
  • No framework runtime adapter is included.
  • Sanchika provides no model runtime or automated compliance judgment.
  • Gallery examples remain synthetic.
  • Physical assistive-technology validation remains necessary.
  • Protected-workspace production depth remains outside the public proof.
  • Real consumer adoption is still incomplete.
  • No dark-mode support claim is made.
  • No universal production-readiness claim is made.

Release Evidence

The detached release execution must replace or resolve the following insertion
points from the final merge commit. This preparation document does not invent
those values.

  • Source commit: f5f86eae29d573576a40c002da7210d7bc7a4dc4

  • Tag: v0.1.1

  • Package files:

    • sanchika-tokens-0.1.1.tgz
    • sanchika-primitives-0.1.1.tgz
    • sanchika-patterns-0.1.1.tgz
  • SHA-256 checksums:

    b8149ced363966fa72c9fbe802c0186e062b3be0a464909ec12799503e601c27  sanchika-tokens-0.1.1.tgz
    08f5ecefe626e65e8ce7656d7409753aa77e07a5467a5ca2876c20d540a6fcec  sanchika-primitives-0.1.1.tgz
    8b50491eaa2d4cdee4f07ec6e742c05253623e7c413d3974800a9bf437af9b83  sanchika-patterns-0.1.1.tgz
    5a4ed39efc912b92d68f8dde500508feda03e92f92bac9e7ba3ae4bc76c7c592  sanchika-gallery-landing-1440x1000.png
    ec7d9f1745e6f53697fa3cafab366bc8930145e9985609df31cb85a7f4e37204  sanchika-gallery-landing-390x844.png
    dbe1c26af8fce29f217669b01be5267cc9a51b99ad4f3f87b6a33ef3e8921cd1  sanchika-gallery-axal-1440x1000.png
    7d3294d139f26c7c672323b1941c0e111364dd4999fd874e7a4bee274b89a56b  sanchika-gallery-pack-1440x1000.png
    ae820e3fd29b18a82b6205b8c18199cd2b3d9862a0bc6b6be56c2f93472c63d6  sanchika-gallery-tools-1440x1000.png
    86e0161e7c2e8834326a9e86266d7f2dcdd8648a42a0be3b9e48628cc3fbece9  sanchika-gallery-forced-colors-768x1024.png
    
  • Package file lists: manifest.jsonpackages[].files[] with archive path
    and byte size from final npm pack --json output

  • Manifest asset: manifest.json

  • Checksum asset: SHA256SUMS

  • Consumer install verification: npm install, runtime probe, and typecheck passed;
    pnpm offline install with exact local tarball overrides, runtime probe, and
    typecheck passed.

Gallery Screenshot Contract

Run pnpm build and pnpm gallery:browser from the release merge commit. The
browser lane uses synthetic data and writes ignored evidence under
output/playwright/s8-gallery-showcase/. Upload these stable release assets:

Release asset Generated source
sanchika-gallery-landing-1440x1000.png release-routes/landing-1440x1000.png
sanchika-gallery-landing-390x844.png release-routes/landing-390x844.png
sanchika-gallery-axal-1440x1000.png release-routes/axal-1440x1000.png
sanchika-gallery-pack-1440x1000.png release-routes/pack-1440x1000.png
sanchika-gallery-tools-1440x1000.png release-routes/tools-1440x1000.png
sanchika-gallery-forced-colors-768x1024.png release-routes/forced-colors-768x1024.png

The release execution checks browser/summary.json against the current gallery
build, validates screenshot bytes and exact filename dimensions, and copies
only the named screenshots into the flat eleven-asset release set.
manifest.json records the tarballs and screenshots; SHA256SUMS covers the
three tarballs and six screenshots. Screenshot metadata is repository-relative
and contains no local path or private data.

Migration And Rollback

See the v0.1.0 to v0.1.1 migration guide
for exact installation URLs, pnpm overrides, unchanged CSS order,
package-backed verification, and rollback to the immutable v0.1.0 assets.