Repository navigation
Add verified installer, signed releases, and original status branding - #7
Merged
Merged
Conversation
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.
Replace GitHub-derived artwork with an original status pulse mark and add a signature-verified manual installer/updater. The README includes a real Chromium popup screenshot using the new mark and separates verified installation, updates, and source builds.
The Bash installer supports macOS/Linux, stable or explicit RC tags, custom permanent folders, and already-downloaded assets. It verifies the checksum list with cosign against the exact repository/release.yml/tag identity and GitHub OIDC issuer, then verifies the ZIP digest before staging files. It preserves the Chrome installation path, keeps a previous copy, restores it if promotion fails, and rejects unsigned packages, unrelated folders, concurrent installs, version mismatches, path traversal, duplicate paths, symlinks, oversized archives, and unsupported file types. No credentials are copied into the extension and no verification bypass is provided. Chrome Load unpacked/Reload remains a user action.
Packaging now includes install.sh and SHA256SUMS covering the ZIP, compatibility checksum, and installer. The dedicated tag-only release workflow adds a separate keyless signing job with contents:read and id-token:write. Only publishing has contents:write. Signatures and checksums are checked before and after uploading all draft assets, before immutable publication. Actions remain pinned; cosign-installer uses its default inputs with no with block or version-resolution step. The README documents the public Sigstore identity/digest metadata emitted by keyless signing even for a private repository.
Version 0.1.1 is prepared for the first signed release. Existing v0.1.0/RC releases remain untouched and are intentionally rejected by the installer because they have no cosign bundle. No release/tag is created by this PR.
Validation: