Skip to content

Sign coverage publish commits#427

Open
kvz wants to merge 1 commit into
mainfrom
sign-coverage
Open

Sign coverage publish commits#427
kvz wants to merge 1 commit into
mainfrom
sign-coverage

Conversation

@kvz
Copy link
Copy Markdown
Member

@kvz kvz commented Jun 6, 2026

Why

The Transloadit verified-commit ruleset now rejects unsigned generated commits. The scheduled CI run on main passed the E2E work, then failed while pushing Static file updates to transloadit/node-sdk-coverage because the generated commit was unsigned.

What changed

  • Adds a required COVERAGE_REPO_SIGNING_SSH_KEY secret for coverage publishing.
  • Signs generated coverage commits with SSH commit signing.
  • Commits as Transloadit Bot <24697610+transloadit-bot@users.noreply.github.com>.
  • Skips coverage publishing on pull request runs.

Signing key status

The private half has been stored as the COVERAGE_REPO_SIGNING_SSH_KEY secret on transloadit/node-sdk. The public half has been added to transloadit-bot as SSH signing key ID 985158.

Validation

The manual run pushed a verified coverage commit to transloadit/node-sdk-coverage:main: transloadit/node-sdk-coverage@b104331

actionlint is not installed locally. Biome intentionally ignores .github/workflows/ci.yml in this repo.

@kvz kvz marked this pull request as ready for review June 6, 2026 09:49
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