Skip to content

feat(_release-rust): opt-in GCP-KMS code signing#97

Draft
emmanuelm41 wants to merge 2 commits into
mainfrom
feat/code-signing
Draft

feat(_release-rust): opt-in GCP-KMS code signing#97
emmanuelm41 wants to merge 2 commits into
mainfrom
feat/code-signing

Conversation

@emmanuelm41

Copy link
Copy Markdown
Member

Draft — part 2 of a 3-repo code-signing rollout. Depends on Zondax/actions PR #12 (references its actions at @v1.2.0).

What

Adds opt-in OS code signing to _release-rust.yml, default off (no change for existing callers):

  • id-token: write added to the workflow's own top-level permissions: (the ceiling — callers can't grant it otherwise).
  • New inputs (enable_signing, notarize_macos, Apple/CODESIGN/PGP config, jsign_sha256, rcodesign_sha256) and signing secrets:.
  • build job: sign macOS (rcodesign) + Windows (jsign/KMS) before Package; sign the Linux archive (.asc) after Package; upload the .asc.
  • Windows GCP auth uses gcp-wif-auth@v1.2.0 with token_format: access_token, create_credentials_file:false, setup_gcloud:false, verify_authentication:false (token-only).

Rollout / dependency

  1. Zondax/actions Adds reusable workflows for Cloud Run #12 → tag v1.2.0.
  2. This PR → merge → tag v10 (carries runner_windows feat(release-rust): opt-in native Windows runner for real -msvc builds #93 + signing).
  3. kunobi-ninja/kache bumps to _workflows@v10.

Notes

  • actionlint clean (only pre-existing SC2086/SC2129 warnings).
  • WIF must be scoped (per-repo allowlist incl. kunobi-ninja/kache, tag-push only) before any real signed run — infra prerequisite, not in this PR.

…sition

Mutable branch refs for end-to-end testing before merge. Flip back to
@v1.2.0 immutable tags before merging this PR.
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