release: v3.3.0 — detection overhaul, graduated anomaly scoring, sync-mirror repair#38
Merged
Conversation
…-mirror repair Assembles the 3.3.0 release from the detection work merged since v3.2.0 (#33-#37) plus the ipinfo-None deprecation fix from the 3.2.1 line. - ipinfo_token/ipinfo_db_path DeprecationWarning no longer fires when the field is explicitly None (spurious warning for callers forwarding an optional setting). - Declare SusPatternsManager._threat_score_threshold and coerce _regex_anomaly to float, fixing the mypy attr-defined / no-any-return errors introduced by #36. - Exclude the async-only attack_simulation harness from unasync mirroring (its data corpus is not Python-transformable) and regenerate the previously-missing sync test mirrors; check-sync is green. - Bump version to 3.3.0 and add CHANGELOG / release-notes entries.
github-actions
Bot
added
documentation
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
1 participant
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.
Summary
Assembles the v3.3.0 release. Bundles the detection work already merged to
mastersince v3.2.0 (#33–#37) with the ipinfo-None deprecation fix from the 3.2.1 line, plus the fixes needed to getmasterCI-green again.What ships in 3.3.0
SecurityConfig.detection_threat_score_threshold(default1.0, so behavior-neutral on upgrade)ipinfo_token/ipinfo_db_pathDeprecationWarningno longer fires when the field is explicitlyNoneFixes to make master releasable
tests/conftest.pywithout regenerating its sync mirror, and feat(attack-sim): attack-simulation benchmark harness (Phase A) #33–feat(detection): B3.1 graduated anomaly-scoring machinery (behavior-neutral) #36 left several sync test mirrors uncommitted — socheck-syncwas red onmaster. Regenerated them. Excluded the async-onlyattack_simulationharness from unasync mirroring (its data corpus isn't Python-transformable, and the generated sync detection engine is already unit-tested — re-benchmarking it in sync is redundant).SusPatternsManager._threat_score_thresholdand coerced_regex_anomalytofloat, fixing theattr-defined/no-any-returnerrors introduced by feat(detection): B3.1 graduated anomaly-scoring machinery (behavior-neutral) #36.Verification (local)
make bump-version VERSION=3.3.0;CHANGELOG.md+docs/release-notes.mdwritten.After merge
Creating the GitHub Release for
v3.3.0triggers the PyPI publish workflow (release.yml,on: release: [created]). Once 3.3.0 is on PyPI I'll follow up on guard-core-app: relock the transitiveguard-core(viafastapi-guard) and regenerate the SecurityConfig catalog.