tikitaki 0.1.6 → 0.1.8
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 +5 -5
- package/README.md +5 -5
- package/package.json +1 -1
package/PUBLISHING.md
CHANGED
|
@@ -61,14 +61,14 @@ A new npm trusted-publisher configuration must complete a successful publish wit
|
|
|
61
61
|
|
|
62
62
|
## Automatic publication through GitHub Actions
|
|
63
63
|
|
|
64
|
-
1. Merge the reviewed change into `main`. The
|
|
65
|
-
2.
|
|
66
|
-
3. The publication job selects the version from
|
|
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
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
|
-
To retry manually, open **Actions →
|
|
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
71
|
|
|
72
|
-
Publication
|
|
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.
|
|
73
73
|
|
|
74
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,12 +1,12 @@
|
|
|
1
1
|
# TikiTaki
|
|
2
2
|
|
|
3
|
-
[](https://github.com/gagarinbefree/TikiTaki/actions/workflows/npm-publish.yml)
|
|
4
|
+
[](https://github.com/gagarinbefree/TikiTaki/releases/latest)
|
|
5
5
|
[](https://www.npmjs.com/package/tikitaki)
|
|
6
6
|
|
|
7
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)
|
|
8
8
|
|
|
9
|
-
**Latest release:** <!-- release-version -->v0.1.
|
|
9
|
+
**Latest release:** <!-- release-version -->v0.1.7<!-- /release-version -->
|
|
10
10
|
|
|
11
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.
|
|
12
12
|
|
|
@@ -290,9 +290,9 @@ No application or maintainer invitation is needed to start contributing. Pick an
|
|
|
290
290
|
|
|
291
291
|
## What happens after merge
|
|
292
292
|
|
|
293
|
-
The [GitHub Actions workflow](./.github/workflows/
|
|
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.
|
|
294
294
|
|
|
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.
|
|
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.
|
|
296
296
|
|
|
297
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.
|
|
298
298
|
|