Skip to content

Add verified installer, signed releases, and original status branding - #7

Merged
cpanato merged 4 commits into
mainfrom
feat/verified-installer
Nov 9, 2026
Merged

cpanato merged 4 commits into
mainfrom
feat/verified-installer

Conversation

@cpanato

@cpanato cpanato commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

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:

  • 17 unit tests and 12 real Chromium tests passed, including status icon colors/transparency and manual refresh behavior.
  • Installer flow tests passed for install/update, custom paths with spaces, exact identity/issuer rejection, checksum failures, unsigned releases, immutable metadata, incorrect versions, unrelated folders, locks, rollback, and unsafe ZIPs.
  • A separate test with real cosign 3.1.4 proves a valid local-key signature without the trusted workflow certificate is rejected; tampered signed checksums also fail. Flow tests use isolated gh/cosign shims; live GitHub OIDC signing is exercised only on a release tag after merge.
  • Typecheck, formatting, ShellCheck, actionlint, release packaging tests, build, ZIP inspection, and all package checksums passed.

@cpanato
cpanato merged commit a2d14a4 into main Nov 9, 2026
1 check passed
@cpanato
cpanato deleted the feat/verified-installer branch November 9, 2026 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant