Repository navigation
release: bump 0.2.0 -> 0.2.1 - #161
Merged
Merged
Conversation
A maintenance release: the copilot and its bindings are unchanged. It ships the
Merging this PR will not alter performance1 warning
Comparing Footnotes |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Pins: wickra-backtest-core =0.2.1, wickra-exchange =0.2.1. Every tracked lockfile takes the family crates at the releases published in this train, wickra-core 2.1.0 included, each resolving once. MSRV and cargo- deny jobs replayed locally: clean.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A maintenance release: the copilot and its bindings are unchanged. It ships the
security fixes in the dependency tree.
Changed
release; the
2.0requirement already admitted it. It addsRunningDrawdownand updates
MaxDrawdownin amortised O(1) with the same values; nothing herecomputes differently.
wickra-backtest-core=0.2.0-> =0.2.1,
wickra-exchange=0.2.0 -> =0.2.1 -- the exact pins thisrepository keeps on its siblings move to the versions those repositories
release in the same train, and every tracked lockfile follows.
wickra-exchange reaches
crypto-bigintandctutilsthroughp256, and thereleases that fix RUSTSEC-2026-0387 and RUSTSEC-2026-0385 require Rust 1.87.
Every earlier crypto-bigint 0.7 release is yanked, so a fresh resolve could no
longer build on 1.86.
with napi-derive-backend 6.1.6, napi-build 2.6.0 and napi-sys 3.4.1; the pair
Dependabot proposed on its own did not compile.
@napi-rs/cli3.10.8 buildsit. All five keep the binding's Rust 1.88 floor.
drops Python 3.8, which the wheels never supported: they still need Python 3.9
or later.
scripts/update-lockfiles.sh.495 indicators the backtest registry resolves -- bar builders, histogram
profiles and a few struct outputs are out of its scope -- rather than the
core's 514 or a stale 497. The counts are now set by the family's count
engine on every release bump.
Security
RUSTSEC-2026-0387, RUSTSEC-2026-0385 and RUSTSEC-2026-0386.
TLS secrets in the
Debugoutput of client session values, application datasent to the outer server after an ECH rejection, Brotli certificate
decompression allocating before authentication, and a ServerHello downgrade to
classical key exchange.
RUSTSEC-2026-0382 and RUSTSEC-2026-0381: certificates chaining through the
distrusted emSign intermediates are refused.
The version moves in every declaration the repository carries; nothing is left at 0.2.0 outside the CHANGELOG history and third-party lock entries.