Skip to content

chore: stamp the 0.6.16 release notes - #488

Merged
Mec-iS merged 2 commits into
mainfrom
release/0.6.16
Oct 12, 2026
Merged

Mec-iS merged 2 commits into
mainfrom
release/0.6.16

Conversation

@Mec-iS

@Mec-iS Mec-iS commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Checklist

  • My branch is up-to-date with main branch.
  • Everything works and tested on latest stable Rust.
  • Coverage and Linting have been applied

Current behaviour

0.6.16 is stamped in Cargo.toml and has a CHANGELOG.md section, but the version was never published to crates.io. Five merged PRs (#475, #478, #481, #482/#483, #485) sit in [Unreleased] or have no entry at all. Separately, the coverage job flaked: the LLVM-instrumented serial run exceeded tarpaulin's default 60 s per-binary timeout while test_logit (a 52181x94 logistic-regression fit) was running.

New expected behaviour

The [Unreleased] section is folded into the existing ## [0.6.16] entry, so the pending patch release ships with complete notes. Cargo.toml stays at 0.6.16. The coverage job now builds in release mode with a 600 s tarpaulin timeout, and test_logit uses a 10000x94 matrix with the same class ratio (418 of 10000 positive) — it finishes in ~0.5 s locally.

Release gates verified locally:

  • cargo test --all-features — 614 unit + 73 doctests, 0 failed
  • cargo fmt --all -- --check
  • cargo clippy --all-features -- -Drust-2018-idioms -Drust-2024-compatibility -Dwarnings
  • cargo +1.85.0 build --all-features (MSRV)
  • cargo package — 146 files, 2.1 MiB

No public-API or serde changes since v0.6.15 (checked git diff v0.6.15..HEAD -- src/), so 0.6.16 stays a valid patch release.

Change logs

Changed

0.6.16 has not been published to crates.io yet, so the [Unreleased]
section is folded into the existing 0.6.16 entry instead of opening
a new version. Covers #475, #478, #481, #482, #485.

All release gates verified locally:
- cargo test --all-features (614 unit + 73 doctests, 0 failed)
- cargo fmt --all -- --check
- cargo clippy --all-features (2018+2024 idioms, -Dwarnings)
- cargo +1.85.0 build --all-features (MSRV)
- cargo package (146 files, 2.1MiB)
The LLVM coverage engine instruments the whole serial test run
(--test-threads 1). On a slow shared runner the instrumented run
could exceed tarpaulin's default 60 s per-binary timeout; observed
as 'Timed out waiting for test response' while test_logit (a
52181x94 logistic-regression fit) was running.

Two changes:
- test_logit now uses a 10000x94 matrix with the same class ratio
  (418 of 10000 positive). The test asserts the same property and
  finishes in ~0.5 s instead of ~3.5 s.
- The coverage job builds in release mode (--release) and raises
  the tarpaulin timeout to 600 s.
@Mec-iS
Mec-iS merged commit 3b62cfc into main Oct 12, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant