Repository navigation
Record the GitHub Packages mirror of 1.0.0 - #34
Merged
Merged
Conversation
@dijo-404/disktop@1.0.0 was published from run 42503754817 after protected approval. The record lists the mirror digest, the identical entries, the clean GitHub Packages install, the verified artifact attestation and npm's own provenance entry, and the package's public, repository-linked visibility. The README gains the GitHub Packages install path; CONTRIBUTING now says the mirror must not be republished.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Records the GitHub Packages mirror publication, adds the GitHub Packages install path to the README, and turns CONTRIBUTING's mirror section into a "published; do not republish" record. It also corrects one claim from #33: npm does sign its own provenance when publishing to GitHub Packages from a job with
id-token: write. That claim appeared in the workflow comment and the release record.Plan traceability
README.md,CONTRIBUTING.md,docs/release-readiness.md) and one comment in.github/workflows/mirror-github-packages.yml.Safety and public behavior
There are no runtime, CLI, JSON, TUI or report changes. The npm
1.0.0release and its record are unchanged.Verification
tests/unit/github-packages-mirror.test.mjsstill passes.prepareandpublishsucceeded. Dijo-404 approvednpm-publish. Published at 2026-11-08 17:13 UTC.gh run downloadpluscompareMirroragainst the npm tarball: every entry identical except the name line. SHA-2561b23622b….gh attestation verify --signer-workflow …/mirror-github-packages.ymlpassed: SLSA v1, sourcee67dc90,workflow_dispatch, run 42503754817 attempt 1. Rekor entries: attestation3758350985, npm provenance3758351012.1.0.0as the latest version, and links this repository.npm test: 1,106 passed.npm audit signaturesis unchecked; that needs aread:packagestoken.