Repository navigation
chore: release v0.23.0 - #515
Merged
Merged
Conversation
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.
Bump the workspace and all inter-crate version pins from 0.22.0 to 0.23.0, sync the workspace, fuzz, and wasm-smoke lockfiles, bump OCSF golden
metadata.product.versionpins and the rstix README install examples, and finalize the CHANGELOG by promoting the[Unreleased]section to[0.23.0]with a TL;DR summary, a compare link, and a release reference link.Once merged, publishing the
v0.23.0GitHub Release triggers the crates.io, binary, and Docker workflows. This release ships the fixes for GHSA-8x2w-m5v2-phxr and GHSA-4q23-jm32-fhr9, which are already public onmain.TL;DR
RSigma v0.23.0 is the "threat intel in the loop" release: rsigma can now pull STIX 2.1 threat intel from TAXII servers or bundle files into a local store and enrich live detections from it,
fieldrefgains string comparisons with pySigma-compatible|neq, and two MCP server vulnerabilities are fixed.--rules-dir(GHSA-8x2w-m5v2-phxr) andevaluate_eventsrefusescommandandhttpenrichers (GHSA-4q23-jm32-fhr9). Upgrade if you runrsigma mcp serve.taxii sync(feat(rsigma): add taxii sync CLI for local FsStore ingest #508) andtaxii store(feat(rsigma): STIX store enrichment and taxii store import #509) import into a local store with validate-on-ingest (feat(rstix): validate-on-ingest for TAXII pages #499), thestixenricher andengine daemon --stix-storeenrich detections from it (feat(rsigma): STIX store enrichment and taxii store import #509), and paginated ingest is tested at ATT&CK scale (feat(rstix): ATT&CK-scale paginated TAXII ingest proof #507) (thanks to @SecurityEnthusiast).fieldrefwithcontains,startswith, andendswith, and|neqnow negates the whole detection item as pySigma does (Support fieldref combined with contains, startswith, and endswith #506, thanks to @Karib0u).build_enrichers_fulltakesEnricherResources(feat(rsigma): STIX store enrichment and taxii store import #509), rstixingest_collectionreturnsIngestReport(feat(rstix): validate-on-ingest for TAXII pages #499), the HIR cache schema is 2 (Support fieldref combined with contains, startswith, and endswith #506), and MCPevaluate_eventsonly acceptstemplateenrichers.rustls0.23.45 for RUSTSEC-2026-0285 (fix(deps): rustls 0.23.45 and cargo-deny ignore cleanup #498, thanks to @SecurityEnthusiast) and Dependabot batches across Rust, CI, the VS Code extension, and docs (chore(deps): batch dependency updates (mid Sep 2026) #491, chore(deps): batch dependency updates (late Sep 2026) #512).Test plan
cargo fmt --all -- --checkcargo clippy --workspace --all-targets --all-features -- -D warningsRUSTDOCFLAGS='-D warnings' cargo doc --workspace --all-features --locked --no-depscargo metadata --lockedfor the workspace,fuzz/, andci/wasm-smoke/cargo test -p rsigma-runtime --test ocsf_golden --lockednpm run docs:buildandnpm run docs:validate