prisma-risk / tsoracle / 26480869009
95%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 89
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 94.938%. Remained the same
26480869009

push

github

web-flow 
chore(release): stabilize all published crates at 1.0.0 (#513)

* chore(release): stabilize all published crates at 1.0.0

Declares API stability across the workspace. From this commit forward
every published crate carries the same semver contract: breaking
changes require a major bump, additive changes a minor, fixes a patch.

- 15 published crates bumped to 1.0.0 (bin, client, codec, consensus,
  core, driver-file, driver-openraft, driver-paxos, failpoint,
  openraft-toolkit, paxos-toolkit, proto, server, standalone, yieldpoint)
- workspace.package.version 0.1.4 → 1.0.0; internal-dep version
  requirements in [workspace.dependencies] updated to match
- all inter-crate path-dep version requirements updated across crates,
  examples, benchmarks, and the kube-e2e driver
- Helm chart appVersion → 1.0.0 (tracks the bin); chart version
  0.1.0 → 0.2.0 (chart shape unchanged, only appVersion edited)
- docs/operations.md and the include_str! copy in tsoracle-server bumped
  to version = "1" in dep snippets

* chore(release): refresh fuzz/Cargo.lock for 1.0.0 bump

The fuzz crate is a standalone Cargo project (workspace-excluded) and
keeps its own Cargo.lock. It depends on the published crates via path,
so the prior commit's 0.x → 1.0.0 bump left lockfile entries stale and
CI's `cargo metadata --locked` failed.

Refreshed via `cd fuzz && cargo update --workspace`; only the 11
tsoracle path-deps changed, no third-party version drift.

13486 of 14205 relevant lines covered (94.94%)

353390.21 hits per line

Jobs
ID Job ID Ran Files Coverage
1 26480869009.1 89
94.94
 GitHub Action Run
Source Files on build 26480869009