26435191251
95%

Ran 26 May 2026 06:06AM UTC

Jobs 1

Files 88

Run time 1min

Badge

Embed ▾

Committed 26 May 2026 06:00AM UTC coverage: 95.462%. Remained the same

Build # 26435191251

Build Type

push

github

Committed by

web-flow

Commit Message

ci(release-plz): sync fuzz/Cargo.lock onto release PR branch (#475)

`fuzz/` is its own cargo workspace (cargo-fuzz convention) and
path-depends on workspace crates. When release-plz bumps a workspace
crate's `[package].version`, fuzz/Cargo.lock keeps the pre-bump pin
because release-plz's workspace `cargo update` never enters the nested
workspace. The CI `fuzz lockfile` guard added in #471 catches this drift
but cannot self-heal — every release PR that bumps a crate `fuzz/`
depends on (e.g. #456) goes red until someone resyncs the lock by hand,
the same way #469 had to.

Wedge a `sync fuzz/Cargo.lock onto release PR` step into the `release-pr`
job right after the release-plz action runs:

  1. Read the action's `prs` output via `env:` (safe, no template
     interpolation into `run:`) and short-circuit if no release PR was
     opened or updated.
  2. Fetch + check out the release branch in the runner.
  3. Run `cargo update --workspace` inside `fuzz/`.
  4. If `fuzz/Cargo.lock` actually changed, commit as `release-plz[bot]`
     and push to the same branch.

The `if git diff --quiet` guard keeps the step idempotent: on release
PRs that don't bump any crate `fuzz/` depends on, the step prints
"already in sync" and exits zero.

Coverage Stats

12979 of 13596 relevant lines covered (95.46%)

407527.15 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	26435191251.1	26 May 2026 06:06AM UTC	88	95.46	GitHub Action Run

prisma-risk / tsoracle / 26435191251
95%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 26435191251

prisma-risk / tsoracle / 26435191251 95%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 26435191251

prisma-risk / tsoracle / 26435191251
95%

README BADGES
x