deps(cargo): bump wickra-core from 0.9.7 to 0.9.9 in the cargo group

[dependabot]

Bumps the cargo group with 1 update: wickra-core.

Updates wickra-core from 0.9.7 to 0.9.9

Release notes

Sourced from wickra-core's releases.

Wickra v0.9.9 — streaming-first technical indicators for 10 languages: native Rust, Python, Node.js, WASM plus a C ABI hub for C, C++, C#, Go, Java, R.

Install

cargo add wickra
pip install wickra
npm install wickra
npm install wickra-wasm
dotnet add package Wickra
go get github.com/wickra-lib/wickra-go

Java (Gradle, Maven Central):

implementation("org.wickra:wickra:0.9.9")

R (r-universe):

install.packages("wickra", repos = "https://wickra-lib.r-universe.dev")

Attached assets

Pre-built artefacts for every supported platform — the same files this workflow run published to crates.io, PyPI, and npm. C# ships to NuGet, Java to Maven Central, Go to the wickra-go module, and R to r-universe via their own release jobs.

• *.whl / wickra-*.tar.gz — Python wheels + sdist (5 platforms, ABI3 ≥ 3.9)
• wickra.*.node — native Node.js bindings (linux-x64-gnu, darwin-x64, darwin-arm64, win32-x64-msvc)
• wickra-*.tgz — npm-pack tarballs (main package + per-platform subpackages + WASM)
• *.crate — cargo source crates (wickra-core, wickra-data, wickra)
• wickra-c-<target>.tar.gz — C ABI: include/wickra.h + wickra.hpp and the cdylib/staticlib per target (linux/macos/windows × x64/arm64), the hub for C, C++, C#, Go, Java and R

Auto-generated changelog

See below; GitHub computes it from the commits since the previous tag.

What's Changed

• release: bump 0.9.8 -> 0.9.9 by @​kingchenc in wickra-lib/wickra#351

... (truncated)

Changelog

Sourced from wickra-core's changelog.

[0.9.9] - 2026-06-28

Maintenance release. No library or binding code changes from 0.9.8; this re-release simply runs through the corrected release workflow (the 0.9.8 npm publish required a hotfix to the napi-rs 3 napi artifacts invocation, now in place), so the published 0.9.9 artifacts are byte-identical to 0.9.8.

[0.9.8] - 2026-06-28

Maintenance release. The library API and every indicator are unchanged from 0.9.7; this release migrates the Node.js binding's build to napi-rs 3 and carries routine dependency and CI tooling updates.

Changed

• Node binding built with napi-rs 3. Migrate napi 2.16 → 3.9, napi-derive 2.16 → 3.5 (Rust) and @napi-rs/cli 2.18 → 3.7 (npm). The published API and every computed value are unchanged — the generated TypeScript surface is identical (626 symbols), only the code-generation format differs. napi 3's derive macros emit #[allow(unsafe_code)], so the Node crate's unsafe_code lint is relaxed from the workspace forbid to deny for that crate only; forbid stays in force for every other crate. The engines.node floor is raised to >= 22 (matching the CI test matrix). ureq is intentionally held at 2.x — ureq 3 unconditionally pulls webpki-root-certs (CDLA-Permissive-2.0), which the native-tls / OS-trust-store setup deliberately avoids.
• Dependency and CI housekeeping. Bump the Maven central-publishing-maven-plugin and the GitHub Actions used by CI (actions/checkout, taiki-e/install-action, actions/setup-java, softprops/action-gh-release). No runtime code changes.

Commits

• 45c11da release: bump 0.9.8 -> 0.9.9 (#351)
• 2ae8976 fix(release): napi-rs CLI 3 renamed 'napi artifacts --dir' to '--output-dir'
• 06b05e6 release: bump 0.9.7 -> 0.9.8 (#350)
• 4ec1082 deps(actions): bump taiki-e/install-action in the github-actions group (#349)
• 13b2ee5 ci(dependabot): split the cargo group — isolate napi, pin ureq to 2.x (#348)
• 025d453 deps(node): migrate the Node binding to napi-rs 3 (#347)
• c6972dd deps(actions): bump the github-actions group with 4 updates (#346)
• 04b10cf deps(maven): bump the maven group across 2 directories with 2 updates (#343)
• 9368c66 docs: add banner + self-made badges to binding READMEs, move title under badg...
• 063a1b5 docs: move the Live demo badge one position forward in the README badge row (...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions