diff --git a/.github/workflows/mirror-github-packages.yml b/.github/workflows/mirror-github-packages.yml index 285c768..d0e6f21 100644 --- a/.github/workflows/mirror-github-packages.yml +++ b/.github/workflows/mirror-github-packages.yml @@ -131,8 +131,8 @@ jobs: SHA256: ${{ needs.prepare.outputs.sha256 }} working-directory: ${{ runner.temp }}/mirror run: echo "$SHA256 dijo-404-disktop-1.0.0.tgz" | sha256sum --check --strict - # npm provenance is an npmjs.org feature; a GitHub artifact attestation - # binds the mirror's digest to this workflow run instead. + # Binds the mirror's digest to this workflow run for `gh attestation + # verify`. npm also signs its own provenance when it publishes below. - uses: actions/attest@1e69f48acb82d1966a394da916b4c1698aa569d6 # v4.2.2 with: subject-path: ${{ runner.temp }}/mirror/dijo-404-disktop-1.0.0.tgz diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f7ec306..8ca836e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -185,29 +185,17 @@ environment unvalidated until a tester supplies the evidence described in the gu ### Mirror 1.0.0 to GitHub Packages -`mirror-github-packages.yml` publishes `@dijo-404/disktop@1.0.0`, which is the npm -tarball with only its package name changed. The -[release record](docs/release-readiness.md#github-packages-mirror) describes what it -checks. Pull requests that touch the workflow or its scripts run its read-only -`prepare` job. Publishing it takes three steps: - -1. Dispatch it from `main`: - - ```sh - gh workflow run mirror-github-packages.yml --ref main -f confirmation='MIRROR 1.0.0' - ``` - -2. Approve the `npm-publish` deployment. The job reads no npm secret. It publishes - with the repository's `GITHUB_TOKEN`, then installs the mirror from GitHub - Packages and requires the same digest. -3. GitHub makes a newly published package **private**. For anyone to install it, - open the package's settings, choose **Change visibility** and select - **Public**. GitHub cannot make a public package private again. - -GitHub Packages refuses a version that already exists, so a rerun cannot replace -the mirror. Do not delete and republish it. Installing needs a token even for a -public package: a personal access token (classic) with `read:packages`, entered -as the password here: +**`@dijo-404/disktop@1.0.0` is already published and public. Do not dispatch the +mirror again, delete it or republish it.** It is the npm tarball with only its +package name changed. `mirror-github-packages.yml` published it in +[run 42503754817](https://github.com/Dijo-404/disktop/actions/runs/42503754817). +The [release record](docs/release-readiness.md#github-packages-mirror) lists what was +checked and the attestation. Pull requests that touch the workflow or its scripts +still run its read-only `prepare` job. A dispatch would stop at the protected +`npm-publish` approval, and GitHub Packages refuses a version that already exists. + +Installing needs a token even for a public package: a personal access token +(classic) with `read:packages`, entered as the password here: ```sh npm login --scope=@dijo-404 --auth-type=legacy --registry=https://npm.pkg.github.com diff --git a/README.md b/README.md index 760bfa9..c6db54e 100644 --- a/README.md +++ b/README.md @@ -36,6 +36,18 @@ npx disktop@1.0.0 # run without installing npm install -g disktop@1.0.0 # or install the `disktop` command ``` +The same release is also on +[GitHub Packages](https://github.com/Dijo-404/disktop/pkgs/npm/disktop) as +`@dijo-404/disktop`. It is identical to the npm package except for its name, and the +command is still `disktop`. GitHub requires a token even for public packages: log +in once, giving a personal access token (classic) with `read:packages` as the +password. + +```sh +npm login --scope=@dijo-404 --auth-type=legacy --registry=https://npm.pkg.github.com +npm install -g @dijo-404/disktop@1.0.0 +``` + Requirements: | | | diff --git a/docs/release-readiness.md b/docs/release-readiness.md index 1141dc2..a28b06a 100644 --- a/docs/release-readiness.md +++ b/docs/release-readiness.md @@ -1,7 +1,9 @@ # 1.0.0 release and validation `disktop@1.0.0` is publicly available on npm, with `latest` pointing to `1.0.0`. -The registry records publication at **2026-10-07 18:05:58.620 UTC**. +The registry records publication at **2026-10-07 18:05:58.620 UTC**. The same +artifact, renamed `@dijo-404/disktop`, has been mirrored on GitHub Packages since +2026-11-08 ([record](#github-packages-mirror)). Engineering and independent postpublication verification passed on 2026-10-07. **Release-owner decision, 2026-10-07:** the remaining real-environment checks for @@ -55,12 +57,18 @@ result unless every other entry keeps its bytes and mode. The workflow then inst that file into a clean prefix and scans with its packaged helper. Only after these checks does the protected `npm-publish` job attest the file and publish it with the repository's `GITHUB_TOKEN`. The unchanged `repository` field links the package to -this repository. GitHub Packages has no npm provenance, so a GitHub artifact -attestation binds the mirror's digest to the publishing run. +this repository. A GitHub artifact attestation binds the mirror's digest to the +publishing run, and npm signed its own provenance statement while publishing. | Evidence | Recorded result | | --- | --- | -| Mirror publication | **Not yet published.** The run, mirror digest, attestation and package visibility are recorded here once the protected job has run. | +| Mirror publication | [Run 42503754817](https://github.com/Dijo-404/disktop/actions/runs/42503754817), dispatched from `main` at merge commit [`e67dc90`](https://github.com/Dijo-404/disktop/commit/e67dc90c4206f15639092b1a33bd2deeaa15f925). `prepare` passed, Dijo-404 approved the `npm-publish` deployment, and [`@dijo-404/disktop@1.0.0`](https://github.com/Dijo-404/disktop/pkgs/npm/disktop) was published to `https://npm.pkg.github.com/` at 2026-11-08 17:13 UTC. Both jobs passed. | +| Mirror artifact | `dijo-404-disktop-1.0.0.tgz`, SHA-256 `1b23622bb611692677ce6d3d22c31bdc0b2dd3cc5dfd717dd6273cecf4ecb302`, integrity `sha512-0vOssSAgXCwbFpTf/7eRoaGM8fsfk4jLvEplxDY4mYSJK4ZDFDSXCjclYSxqWDoJDDE/LCzRS5tFc+FPiMenyg==`, 192 files. Apart from the `name` line of `package.json`, every entry has the bytes and mode of the npm tarball `a2deddd7…`; this was rechecked separately against the run's uploaded artifact. | +| Pre-publication consumer | The same file installed into a clean prefix and reported `1.0.0`. Its packaged helper passed its checksum check and completed a scan. | +| GitHub Packages consumer | The published package downloaded from GitHub Packages with the same SHA-256. A clean install resolved it from `npm.pkg.github.com` with matching integrity and reported `1.0.0`. | +| Artifact attestation | [Attestation 65087055](https://github.com/Dijo-404/disktop/attestations/65087055): SLSA v1 build provenance, Rekor entry `3758350985`, integrated 17:13:41 UTC. A separate `gh attestation verify` confirmed the subject digest, the signer `mirror-github-packages.yml@refs/heads/main`, source commit `e67dc90`, the `workflow_dispatch` trigger and run 42503754817 attempt 1. | +| npm provenance | `npm publish` signed a provenance statement from the job's OIDC identity: Rekor entry `3758351012`, integrated 17:13:43 UTC. Whether GitHub Packages serves it to `npm audit signatures` has not been checked. | +| Visibility and link | The [package page](https://github.com/Dijo-404/disktop/pkgs/npm/disktop) is visible without signing in and links this repository. Installing still requires a GitHub token with `read:packages`. | | Open advisories at mirroring | RustSec published RUSTSEC-2026-0391, -0398, -0403 and -0410 (plus unsoundness warnings) against `zstd` 0.14.0, `zstd-safe` 8.0.0 and `zstd-sys` 2.1.0 on 2026-10-16, after `1.0.0` passed its advisory gate. The helper in both the npm package and the mirror is that `1.0.0` build. It creates one encoder or decoder per operation over files it wrote itself, and does not use the seekable, dictionary, training, `StableInBuffer` or WebAssembly paths the advisories name. The release owner approved mirroring the unchanged artifact on 2026-11-08; a fix needs a separately authorised maintenance release. npm's open advisories at that date affected development dependencies only. | ## Executed gates