@jack.winter/pancake-ui 0.1.0 → 0.1.1
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/CHANGELOG.md +7 -2
- package/README.md +1 -1
- package/docs/installation.md +5 -5
- package/docs/verification.md +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,8 +1,13 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## 0.1.1
|
|
4
4
|
|
|
5
|
-
-
|
|
5
|
+
- Clarify registry installation and the first trusted-publisher release deadline.
|
|
6
|
+
- Validate GitHub trusted publishing using the verified package archive. No runtime component changes.
|
|
7
|
+
|
|
8
|
+
## 0.1.0
|
|
9
|
+
|
|
10
|
+
- Publish the first npm release as `@jack.winter/pancake-ui@0.1.0`, with MIT code licensing and retained SIL Open Font License notices for Inter. Migrate consumer imports to the scoped name.
|
|
6
11
|
- Add a manual trusted-publishing workflow that publishes the exact verified main-branch archive, with source, checksum, package metadata, and license checks.
|
|
7
12
|
|
|
8
13
|
- Run CI once per PR revision, cancel superseded PR runs, share build outputs across parallel browser jobs, and retain a required gate for all checks.
|
package/README.md
CHANGED
|
@@ -17,7 +17,7 @@ npm install @jack.winter/pancake-ui
|
|
|
17
17
|
for an unpublished change, download `pancake-ui-package` from a successful main-branch [Verify run](https://github.com/j4ckwinter/pancake-ui/actions/workflows/verify.yml). extract the ZIP into your app’s `vendor/pancake-ui/` folder, then install the archive:
|
|
18
18
|
|
|
19
19
|
```sh
|
|
20
|
-
npm install ./vendor/pancake-ui/jack.winter-pancake-ui-0.1.
|
|
20
|
+
npm install ./vendor/pancake-ui/jack.winter-pancake-ui-0.1.1.tgz
|
|
21
21
|
```
|
|
22
22
|
|
|
23
23
|
use the filename you downloaded, and commit the archive, manifest, and app lockfile alongside `package.json`. see [installation and releases](docs/installation.md) for local builds, upgrades, and registry release setup.
|
package/docs/installation.md
CHANGED
|
@@ -10,7 +10,7 @@ Use React and React DOM 19.2+ within React 19, Node 22.18+, and an ESM bundler s
|
|
|
10
10
|
npm install @jack.winter/pancake-ui
|
|
11
11
|
```
|
|
12
12
|
|
|
13
|
-
Commit the app’s `package.json` and lockfile. For an exact version, use `npm install --save-exact @jack.winter/pancake-ui@0.1.
|
|
13
|
+
Commit the app’s `package.json` and lockfile. For an exact version, use `npm install --save-exact @jack.winter/pancake-ui@0.1.1`.
|
|
14
14
|
|
|
15
15
|
### Install a verified archive
|
|
16
16
|
|
|
@@ -20,7 +20,7 @@ Successful **push runs on main** in [Verify](https://github.com/j4ckwinter/panca
|
|
|
20
20
|
2. Install the **`.tgz` inside the ZIP**, from your app's root:
|
|
21
21
|
|
|
22
22
|
```sh
|
|
23
|
-
npm install ./vendor/pancake-ui/jack.winter-pancake-ui-0.1.
|
|
23
|
+
npm install ./vendor/pancake-ui/jack.winter-pancake-ui-0.1.1.tgz
|
|
24
24
|
```
|
|
25
25
|
|
|
26
26
|
Use the filename from your download if its version differs. The app needs React and React DOM installed; an existing React app normally already has them. No library clone, Playwright, Tailwind or library build is needed.
|
|
@@ -29,7 +29,7 @@ With [GitHub CLI](https://cli.github.com/) installed and authenticated, you can
|
|
|
29
29
|
|
|
30
30
|
```sh
|
|
31
31
|
gh run download RUN_ID --repo j4ckwinter/pancake-ui --name pancake-ui-package --dir vendor/pancake-ui
|
|
32
|
-
npm install ./vendor/pancake-ui/jack.winter-pancake-ui-0.1.
|
|
32
|
+
npm install ./vendor/pancake-ui/jack.winter-pancake-ui-0.1.1.tgz
|
|
33
33
|
```
|
|
34
34
|
|
|
35
35
|
Commit the downloaded archive, `packed.json`, your app's `package.json`, and its lockfile. Fresh clones can then use `npm ci` without GitHub credentials. Record the source run URL when upgrading, use a new package version, and do not overwrite an archive already used by an app. GitHub artifacts expire after 90 days (or earlier if deleted); keeping the archive in your app makes it independent of that retention period. See [GitHub's artifact download instructions](https://docs.github.com/en/actions/how-tos/manage-workflow-runs/download-workflow-artifacts).
|
|
@@ -111,7 +111,7 @@ npx playwright install chromium firefox webkit
|
|
|
111
111
|
npm run release:local
|
|
112
112
|
```
|
|
113
113
|
|
|
114
|
-
This runs full verification and produces `artifacts/jack.winter-pancake-ui-0.1.
|
|
114
|
+
This runs full verification and produces `artifacts/jack.winter-pancake-ui-0.1.1.tgz`, its SHA-256 checksum and a release manifest recording the source commit and whether the working tree was dirty. Copy the archive into the consuming app's `vendor/pancake-ui/` directory and install it as above. Ordinary `npm pack` builds an archive but does not run the full verification suite.
|
|
115
115
|
|
|
116
116
|
## Versioning releases
|
|
117
117
|
|
|
@@ -134,7 +134,7 @@ Local releases do not publish to a registry or upload to GitHub. Bundled Inter f
|
|
|
134
134
|
|
|
135
135
|
Publication uses the separate [Publish workflow](https://github.com/j4ckwinter/pancake-ui/actions/workflows/publish.yml). It publishes the exact archive from a successful main-branch Verify run, without rebuilding or repacking. The source revision must still be the current main revision. The workflow validates the source run, archive checksum, contents, package identity, version, MIT license, and public npm destination before publication.
|
|
136
136
|
|
|
137
|
-
The first release needs an npm account with access to the `@jack.winter` scope. Bootstrap the package once by authenticating to npm and publishing the reviewed, verified archive; never commit credentials. Configure the package’s npm trusted publisher for GitHub Actions with owner `j4ckwinter`, repository `pancake-ui`, and workflow filename `publish.yml`. This workflow does not use a GitHub environment. Subsequent workflow publishes use OIDC and provenance, without a stored npm token.
|
|
137
|
+
The first release needs an npm account with access to the `@jack.winter` scope. Bootstrap the package once by authenticating to npm and publishing the reviewed, verified archive; never commit credentials. Configure the package’s npm trusted publisher for GitHub Actions with owner `j4ckwinter`, repository `pancake-ui`, and workflow filename `publish.yml`. This workflow does not use a GitHub environment. Subsequent workflow publishes use OIDC and provenance, without a stored npm token. Complete the first workflow release within two days of creating the trusted publisher; npm expires configurations that have not completed their first publish. See [npm’s configuration expiry policy](https://docs.npmjs.com/trusted-publishers/#trusted-publisher-configuration-expiry).
|
|
138
138
|
|
|
139
139
|
After a new version has been merged and Verify has succeeded on current main, dispatch Publish on main using that Verify run’s numeric ID:
|
|
140
140
|
|
package/docs/verification.md
CHANGED
|
@@ -52,7 +52,7 @@ Repository instructions are guidance, not a security boundary. GitHub separately
|
|
|
52
52
|
|
|
53
53
|
The configured repository is [j4ckwinter/pancake-ui](https://github.com/j4ckwinter/pancake-ui). The main-branch policy is recorded in `.github/main-ruleset.json`: zero required approving reviews, no latest-push approval, resolved discussions, and the GitHub Actions `verify` check on an up-to-date branch. Force pushes and deletion are blocked, with no bypass actors. The [active GitHub ruleset](https://github.com/j4ckwinter/pancake-ui/rules/26247432) was read back on 2026-10-31 after the initial push. Check the [workflow runs](https://github.com/j4ckwinter/pancake-ui/actions/workflows/verify.yml) for current hosted results; a local green run does not establish hosted CI success.
|
|
54
54
|
|
|
55
|
-
After verification succeeds on a push to `main`, the workflow uploads the tested `.tmp/package` archive and its SHA-256/file manifest as `pancake-ui-package`. It does not rebuild or repack after testing. Pull-request runs and failed verification do not upload a consumer package. Artifacts are retained for 90 days
|
|
55
|
+
After verification succeeds on a push to `main`, the workflow uploads the tested `.tmp/package` archive and its SHA-256/file manifest as `pancake-ui-package`. It does not rebuild or repack after testing. Pull-request runs and failed verification do not upload a consumer package. Artifacts are retained for 90 days. Consumers normally install the npm release and commit their lockfile; vendor the archive only when testing an unpublished change. Verify does not publish to npm. The separate manually dispatched Publish workflow validates and publishes that exact archive using npm trusted publishing; see [release setup](installation.md#publish-a-verified-release).
|
|
56
56
|
|
|
57
57
|
## Dedicated component stories
|
|
58
58
|
|