prisma-risk / tsoracle / 26421572889
95%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 77
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: 95.858% (+0.008%) from 95.85%
26421572889

push

github

web-flow 
fix: ship per-crate READMEs to crates.io (#451)

The workspace defined `readme = "README.md"` under [workspace.package].
When inherited via `readme.workspace = true`, that path resolves relative
to the workspace root (`../../README.md`), not the crate directory, so
every library crate pointed at the root marketing README. Cargo only
shipped the per-crate README by accidental shadowing of a same-named
local file, which is cargo-version-dependent.

Two symptoms followed:

- `tsoracle` (the bin) and `tsoracle-standalone` set no `readme` field and
  had no README of their own, so crates.io rendered no README at all.
- `tsoracle-server` published the root README, whose logo uses a relative
  path (`site/static/...`); crates.io rewrites relative image URLs against
  the crate manifest path, so the logo 404s on the crate page.

Fix the configuration at the root:

- Drop `readme` from [workspace.package].
- Set explicit crate-relative `readme = "README.md"` on every published
  crate (including the two drivers that previously relied on autodetect),
  so each crate ships its own README and fails loud if it is missing.
- Add crate-specific READMEs for `tsoracle` and `tsoracle-standalone`.

Verified with `cargo package`: the `../../README.md` warning is gone, the
`tsoracle` tarball now contains a README, and `tsoracle-server` bundles its
own crate README with no image references.

11271 of 11758 relevant lines covered (95.86%)

443049.54 hits per line

Jobs
ID Job ID Ran Files Coverage
1 26421572889.1 77
95.86
 GitHub Action Run
Source Files on build 26421572889