Skip to content

release(4.4.0): lockstep core engines at 4.4.0 - #151

Merged
rennf93 merged 1 commit into
masterfrom
release/4.4.0
Oct 15, 2026
Merged

release(4.4.0): lockstep core engines at 4.4.0#151
rennf93 merged 1 commit into
masterfrom
release/4.4.0

Conversation

@rennf93

@rennf93 rennf93 commented Oct 15, 2026

Copy link
Copy Markdown
Member

Delivers issue: #150

Closes #150

Description

Bumps the workspace to 4.4.0 with make bump-version (crate manifests, workspace pins, Cargo.lock) and turns the Unreleased CHANGELOG section into 4.4.0, adding the Breaking list and the Fixed entries that were missing (Cookie pair scan, passive log reason, dynamic rule versions over the base config, the semantic header opt-out). The VERSION test follows the bump.

Motivation and Context

Lockstep minor release 4.4.0 across the core engines. Publishing is tag driven and happens separately, guard-core-engine first, then guard-core-rs.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation change
  • Performance improvement
  • Code cleanup or refactoring

How Has This Been Tested

CI: lint, workspace tests, conformance, docs, coverage gate and the MSRV job.

Checklist:

  • My code follows the code style of this project
  • All new and existing tests passed
  • I have updated the version number if necessary

@github-actions github-actions Bot added documentation Docs site, README, CHANGELOG, license files benchmarks Criterion benches, fuzz targets, performance comparisons build Workspace manifests, toolchain config, linters, Docker dependencies Cargo.toml or Cargo.lock area: engine Touches crates/guard-core-engine/ (compiler, preprocessor, semantic, detect, patterns) area: facade Touches crates/guard-core-rs/ (published facade crate) area: python-bindings Touches crates/guard-core-python/ (PyO3 detection bindings) area: conformance Touches the spec 4.0.2 corpus, ledger, or xfail baseline labels Oct 15, 2026
@rennf93 rennf93 mentioned this pull request Oct 15, 2026
Merged
4 of 9 tasks
@rennf93
rennf93 merged commit be51b52 into master Oct 15, 2026
20 checks passed
@rennf93
rennf93 deleted the release/4.4.0 branch October 15, 2026 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

area: conformance Touches the spec 4.0.2 corpus, ledger, or xfail baseline area: engine Touches crates/guard-core-engine/ (compiler, preprocessor, semantic, detect, patterns) area: facade Touches crates/guard-core-rs/ (published facade crate) area: python-bindings Touches crates/guard-core-python/ (PyO3 detection bindings) benchmarks Criterion benches, fuzz targets, performance comparisons build Workspace manifests, toolchain config, linters, Docker dependencies Cargo.toml or Cargo.lock documentation Docs site, README, CHANGELOG, license files

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

release(4.4.0): lockstep core engines at 4.4.0

1 participant

@rennf93