Skip to content

chore: prepare 1.3 cleanup on restored main#68

Open
ebursztein wants to merge 3 commits into
mainfrom
release/1.3-cleanup-pr-v2
Open

chore: prepare 1.3 cleanup on restored main#68
ebursztein wants to merge 3 commits into
mainfrom
release/1.3-cleanup-pr-v2

Conversation

@ebursztein
Copy link
Copy Markdown
Collaborator

Summary

  • preserves the repaired main history while applying the trusted 1.3 cleanup tree
  • removes the retired PolicyCallback/callback event-type rail so SecurityEvent uses RuntimeSecurityEventType directly
  • deletes stale positive Policy V2 E2E tests and keeps stale event strings only in rejection tests
  • updates security action benchmarks to exercise SecurityRuleSet/plugin paths

Verification

  • cargo check -p capsem-core --no-default-features
  • cargo check -p capsem-service --no-default-features
  • cargo test -p capsem-core --no-default-features security_event --lib
  • cargo test -p capsem-logger --no-default-features security_rule --lib
  • cargo test -p capsem-service --no-default-features --lib
  • cargo test -p capsem-core --no-default-features --lib
  • cargo test -p capsem-logger --no-default-features --lib
  • cargo check -p capsem-core --no-default-features --bench security_actions

Notes

The first commit is a merge-style snapshot: parent one is repaired origin/main, parent two is release/1.3-cleanup-pr, and the tree starts from the trusted cleanup branch. The follow-up burn pass removes the stale callback event identity layer instead of preserving compatibility.

Preserve the repaired main history while making the trusted 1.3 cleanup tree explicit.\n\nThe first parent is restored origin/main. The second parent is release/1.3-cleanup-pr. The resulting tree is exactly release/1.3-cleanup-pr, so old policy/setup compatibility paths are not reintroduced by a content merge.
@codecov-commenter
Copy link
Copy Markdown

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants