Skip to content

P1: Proxy checksum verification robustness (deterministic source) #21

Closed

Description

@Kinin-Code-Offical
No description provided.

Activity

  1. Kinin-Code-Offical commented on Dec 22, 2025

    @Kinin-Code-Offical
    OwnerAuthor

    Plan:

    • Replace release-body checksum parsing with deterministic checksum fetch from GCS (.sha256 sidecar for proxy binary).
    • Fail fast with clear error if checksum file missing or malformed.
    • Keep GitHub release lookup for tag validation; remove body parsing dependency.

    Risks:

    • If GCS checksum file is unavailable for a version, proxy update will fail instead of skipping verification.

    Tests:

    • npm ci
    • npm run lint
    • npm test
    • npm run build
    • npm run package
    • npm run smoke:exe
  2. Kinin-Code-Offical commented on Dec 22, 2025

    @Kinin-Code-Offical
    OwnerAuthor

    PR merged: #38
    Merge commit: ab17c22
    Tests: npm ci, npm run lint, npm test, npm run build, npm run package, npm run smoke:exe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions