tamada / oinkie / 34016851153
97%
main: 97%

LAST BUILD BRANCH: releases/v0.5.0
DEFAULT BRANCH: main
Ran
Jobs 1
Files 20
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: 96.683%. Remained the same
34016851153

Pull #101

github

tamada 
fix: give the version script a working directory and say what it needs

Two of review's points, one of which is right for a reason other than
the one given.

`cargo update` is not what introduced a working-directory assumption.
Every path in this script is relative and always was, so running it from
anywhere else already failed at the first sed with `Cargo.toml: No such
file or directory`. The observation stands even so: the precondition was
never declared. It is now removed rather than documented -- the script
goes to the repository root, derived from its own location, and works
from anywhere.

The dependency on cargo is new, and `cargo: not found` three-quarters of
the way through a release explains nothing. It says what it needs and
why, and it says so before the first rewrite, so a machine without cargo
does not end up with a half-bumped tree.

The release note bullet was not truncated -- no bullet in that file ends
with a full stop -- but it did end on a participial phrase, which is why
it read as cut off. Reworded to end on a clause.

Verified: run from /tmp it finds the repository and bumps it; with cargo
hidden from PATH it exits 1, says why, and leaves all four files
untouched; from the repository root the happy path is unchanged and
`cargo build --locked` passes.

Reported by Copilot on #101.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pull Request #101: fix: sync Cargo.lock when the version is bumped

5305 of 5487 relevant lines covered (96.68%)

48.33 hits per line

Jobs
ID Job ID Ran Files Coverage
1 34016851153.1 20
96.68
 GitHub Action Run
Source Files on build 34016851153