tamada / oinkie / 33608158741
97%
main: 97%

LAST BUILD BRANCH: releases/v0.4.0
DEFAULT BRANCH: main
Ran
Jobs 1
Files 14
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.64%. Remained the same
33608158741

Pull #76

github

tamada 
fix: anchor the version replace to what it is replacing

update_version.sh rewrote the version with a global replace of the bare
number over README.md and docs/content/_index.md, so any text that
happened to contain the old version was rewritten whether or not it was
a version.

Measured against README.md at 25e5e3d, running the script's sed for
0.3.0 -> 0.4.0:

  cir.nii.ac.jp/crid/1572824500.3.007232  ->  ...500.4.007232

the NII CRID of a cited paper, because 500.3.00 contains 0.3.0. That
link would have broken silently, in the README, in a release. It did not
happen only because #74 bumps the files by hand, leaving the script
nothing to do.

Each of the three replacements is anchored now -- the version badge, the
release-tag link, and the container tag -- and matches the shape of a
version rather than the literal previous one. Cargo.toml was already
anchored and is unchanged in behaviour.

Matching a shape also makes the script idempotent: it no longer depends
on Cargo.toml still holding the old version when it runs, which is
exactly the state it will find on the release branch.

Verified on a copy of the tree at 25e5e3d. The script now produces
Cargo.toml, README.md and docs/content/_index.md byte-identical to what
#74 wrote by hand, leaves the CRID alone, and changes nothing on a
second run.

Closes #75

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pull Request #76: fix: anchor the version replace to what it is replacing

4487 of 4643 relevant lines covered (96.64%)

32.98 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33608158741.1 14
96.64
 GitHub Action Run
Source Files on build 33608158741