DrudgeCAS / gristmill / 31930209411
92%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 4
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: 91.244%. Remained the same
31930209411

push

github

chenpeizhi 
ci: Release with release-please

Same setup as drudge: a workflow on master, a config and a manifest.  The
version lives in `pyproject.toml`, `CITATION.cff` and `uv.lock`, and CI runs
`uv sync --locked`, so the workflow refreshes the lock on the release branch
after release-please has written the bump.

Two deviations from drudge, both deliberate.

`CITATION.cff` carries `x-release-please-version` and
`x-release-please-date` annotations.  Listing a file under `extra-files` is
not enough on its own: the generic updater only rewrites lines carrying an
annotation, so without them the file is left behind.  Drudge's is at 0.11.0
while the package is at 0.11.2 for exactly this reason.

`bump-minor-pre-major` is on.  The scikit-build migration is a breaking
change, and below 1.0.0 release-please answers a breaking change with 1.0.0
by default.  The package is classified Beta, so the first release should be
0.10.0 rather than a claim of a stable interface.

`bootstrap-sha` is the last commit before the conventional-commit history, so
the first changelog covers everything since, back to the scikit-build
migration.  The manifest starts at 0.9.0, the current unreleased version in
`pyproject.toml`.

Verified with `release-please release-pr --dry-run`: it proposes 0.10.0, and
the generic updater moves both the version and the date in `CITATION.cff`.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

1782 of 1953 relevant lines covered (91.24%)

0.91 hits per line

Jobs
ID Job ID Ran Files Coverage
1 31930209411.1 4
91.24
 GitHub Action Run
Source Files on build 31930209411