tikitaki 0.1.5 → 0.1.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/PUBLISHING.md CHANGED
@@ -59,14 +59,16 @@ The repository includes `.github/workflows/npm-publish.yml`. Its job uses a GitH
59
59
 
60
60
  A new npm trusted-publisher configuration must complete a successful publish within two days or it expires. Enable direct `npm publish` explicitly: current npm settings may otherwise allow only staged publication. See the [official trusted publishing guide](https://docs.npmjs.com/trusted-publishers/).
61
61
 
62
- ## Subsequent publication through GitHub Actions
62
+ ## Automatic publication through GitHub Actions
63
63
 
64
- 1. Merge the reviewed change into `main` and wait for the full tests/build/Pages/Release workflow to pass.
65
- 2. Open **Actions → Publish npm packages → Run workflow** on `main`.
66
- 3. Enter the existing stable release tag, for example `v0.1.5`.
67
- 4. Approve the `npm` environment if configured. The job downloads the release archives, verifies their checksums and version, and publishes them in dependency order using OIDC.
64
+ 1. Merge the reviewed change into `main`. The **Test, build and release** workflow runs tests, builds packages, deploys Pages, and creates the GitHub Release.
65
+ 2. The same run contains a separate **Publish npm packages** job after **Publish GitHub Release**. Failed, cancelled, pull-request, and fork runs cannot publish.
66
+ 3. The publication job selects the exact version from this run's build output. It does not guess from the latest release, so a newer release cannot change the publication target.
67
+ 4. The job downloads those release archives, verifies checksums and version, and publishes the core followed by all four adapters through OIDC.
68
68
  5. Verify registry metadata and test installation in a clean application before announcing the release.
69
69
 
70
- Publication runs are serialized and are not cancelled midway by a newer publication request. Ordinary CI runs still cancel outdated tests and builds on the same branch. Publication is manual rather than triggered by every demo deployment.
70
+ To retry manually, open **Actions → Test, build and release → Run workflow** on `main` and enter the existing stable release tag. Previously published identical archives are skipped. The workflow filename and `npm` environment are unchanged, so the existing npm Trusted Publisher settings continue to apply.
71
+
72
+ Publication jobs are serialized. A newer commit cancels an outdated pipeline on the same branch, including any running publication job. If publication was interrupted, retry its existing release tag manually: identical published archives are skipped safely. Leave the manual tag empty to run the full pipeline. A manual publication by tag skips tests, builds, Pages, and release creation.
71
73
 
72
74
  After the initial packages exist, verify that the README installation commands resolve the intended public packages. Keep package metadata, adapter guides, and the registry pages consistent.
package/README.md CHANGED
@@ -1,11 +1,12 @@
1
1
  # TikiTaki
2
2
 
3
- [![Tests and build](https://github.com/gagarinbefree/TikiTaki/actions/workflows/ci-pages.yml/badge.svg?branch=main)](https://github.com/gagarinbefree/TikiTaki/actions/workflows/ci-pages.yml)
4
- [![Release](docs/badges/release.svg?version=0.1.4)](https://github.com/gagarinbefree/TikiTaki/releases/latest)
3
+ [![Tests and build](https://github.com/gagarinbefree/TikiTaki/actions/workflows/npm-publish.yml/badge.svg?branch=main)](https://github.com/gagarinbefree/TikiTaki/actions/workflows/npm-publish.yml)
4
+ [![Release](docs/badges/release.svg?version=0.1.6)](https://github.com/gagarinbefree/TikiTaki/releases/latest)
5
+ [![npm version](https://img.shields.io/npm/v/tikitaki.svg)](https://www.npmjs.com/package/tikitaki)
5
6
 
6
7
  [Live demo](https://gagarinbefree.github.io/TikiTaki/) · [Releases](https://github.com/gagarinbefree/TikiTaki/releases) · [Report an issue](https://github.com/gagarinbefree/TikiTaki/issues/new)
7
8
 
8
- **Latest release:** <!-- release-version -->v0.1.4<!-- /release-version -->
9
+ **Latest release:** <!-- release-version -->v0.1.6<!-- /release-version -->
9
10
 
10
11
  TikiTaki is a TypeScript library for swipe navigation through a two-dimensional grid whose rows can have different lengths. Use it for paged interfaces, galleries, stories, or component-based feeds. You supply the content; TikiTaki handles navigation, pointer gestures, animation, and cell lifecycle.
11
12
 
@@ -289,9 +290,9 @@ No application or maintainer invitation is needed to start contributing. Pick an
289
290
 
290
291
  ## What happens after merge
291
292
 
292
- The [GitHub Actions workflow](./.github/workflows/ci-pages.yml) validates pull requests and pushes to `main`. It runs type checks, lint, formatting, unit/integration tests, package validation, production builds, and Chrome desktop/touch E2E. PR runs do not publish upstream releases or deploy upstream Pages. A new commit cancels the earlier pipeline for the same branch or PR.
293
+ The [GitHub Actions workflow](./.github/workflows/npm-publish.yml) validates pull requests and pushes to `main`. It runs type checks, lint, formatting, unit/integration tests, package validation, production builds, and Chrome desktop/touch E2E. PR runs do not publish upstream releases or deploy upstream Pages. A new commit cancels the earlier pipeline for the same branch or PR.
293
294
 
294
- After a successful `main` run, the tested demo artifact is deployed to [GitHub Pages](https://gagarinbefree.github.io/TikiTaki/) and a matching [GitHub Release](https://github.com/gagarinbefree/TikiTaki/releases) is created. Stable release versions advance by one patch, such as `v0.1.1` → `v0.1.2`. The release includes the demo archive, `version.json`, npm package tarballs, and their integrity manifest. A bot updates the README badge and package versions. npm publication is a separate maintainer action after first-time account setup. Contributors do not need to edit those generated release fields in feature PRs.
295
+ After a successful `main` run, the tested demo artifact is deployed to [GitHub Pages](https://gagarinbefree.github.io/TikiTaki/) and a matching [GitHub Release](https://github.com/gagarinbefree/TikiTaki/releases) is created. Stable release versions advance by one patch, such as `v0.1.1` → `v0.1.2`. The release includes the demo archive, `version.json`, npm package tarballs, and their integrity manifest. A bot updates the README badge and package versions. The same run then shows a separate **Publish npm packages** job, which automatically publishes all five verified packages through the trusted publisher. A manual run remains available for retries. Contributors do not need to edit those generated release fields in feature PRs.
295
296
 
296
297
  If you want Pages for your own fork, enable Actions, select **Settings → Pages → Source → GitHub Actions**, and allow the `github-pages` environment to deploy from your fork's `main`. If you rename the repository, update `DEPLOYMENT_CONFIG.basePath` in [tooling.config.mjs](./tooling.config.mjs). Fork deployments and releases belong to the fork; upstream releases follow the upstream workflow.
297
298
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tikitaki",
3
- "version": "0.1.5",
3
+ "version": "0.1.7",
4
4
  "description": "Zero-runtime-dependency navigation for a ragged 2D swipe grid",
5
5
  "type": "module",
6
6
  "types": "./dist/index.d.ts",