chore(deps): bump scirs2-text from 0.6.3 to 0.6.4

[dependabot]

Bumps scirs2-text from 0.6.3 to 0.6.4.

Release notes

Sourced from scirs2-text's releases.

SciRS2 0.6.4 Release

[0.6.4] - 2026-07-28

Follow-up release completing the wasm32 fix from 0.6.3's Windows-hardening cycle. The oxifft 0.4.1 bump landed a hard compile_error! for its threading (rayon) feature on wasm32 targets; the fix was merged before the 0.6.3 tag was cut, but arrived too late to affect the scirs2-fft/scirs2-signal artifacts actually published to crates.io at 0.6.3 — those had already gone out with the unfixed manifest, which blocked scirs2-wasm's own publish and, transitively, the scirs2 meta-crate's. Both were skipped from 0.6.3 as a result; this release publishes them.

Fixed

• scirs2-fft / scirs2-signal: oxifft's threading (rayon) feature is no longer enabled by default on wasm32-unknown-unknown. Both crates now declare oxifft via target-gated [target.'cfg(...)'.dependencies] tables — full defaults (std + threading) off-wasm, default-features = false, features = ["std"] on wasm32 — resolving the hard compile_error! introduced by oxifft 0.4.1.

Published

• scirs2-wasm and scirs2 (the meta-crate) resume publishing at 0.6.4, catching up after being skipped at 0.6.3 due to the issue above. All 33 workspace crates are now uniformly at 0.6.4.

Full Changelog: cool-japan/scirs@v0.6.3...v0.6.4

Changelog

Sourced from scirs2-text's changelog.

[0.6.4] - 2026-07-28

Follow-up release completing the wasm32 fix from 0.6.3's Windows-hardening cycle. The oxifft 0.4.1 bump landed a hard compile_error! for its threading (rayon) feature on wasm32 targets; the fix was merged before the 0.6.3 tag was cut, but arrived too late to affect the scirs2-fft/scirs2-signal artifacts actually published to crates.io at 0.6.3 — those had already gone out with the unfixed manifest, which blocked scirs2-wasm's own publish and, transitively, the scirs2 meta-crate's. Both were skipped from 0.6.3 as a result; this release publishes them.

Fixed

• scirs2-fft / scirs2-signal: oxifft's threading (rayon) feature is no longer enabled by default on wasm32-unknown-unknown. Both crates now declare oxifft via target-gated [target.'cfg(...)'.dependencies] tables — full defaults (std + threading) off-wasm, default-features = false, features = ["std"] on wasm32 — resolving the hard compile_error! introduced by oxifft 0.4.1.

Published

• scirs2-wasm and scirs2 (the meta-crate) resume publishing at 0.6.4, catching up after being skipped at 0.6.3 due to the issue above.

---

Commits

• a70fec3 Availability of 0.6.4
• See full diff 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)