Add security-7-migration module: Spring Security 6.5.11 vs 7.1.2 jar diff, compile checks and runtime probes

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01YPgGH6aMbSLANL3E2HHmS6
This commit is contained in:
2026-10-25 19:00:27 +00:00
co-authored by Claude Sonnet 5.5
parent d1b9339951
commit e47787ecaa
25 changed files with 1428 additions and 0 deletions
+17
View File
@@ -0,0 +1,17 @@
# security-7-migration
Spring Security **6.5.11** against **7.1.2**: the jars compared class by class, Security 6 code compiled against both
lines, and two small programs run on both. Companion to the migration guide on [ankurm.com](https://ankurm.com).
| script | writes |
|---|---|
| `scripts/api_diff.py` | `output/01-versions-and-baseline.txt`, `output/02-removed-api.txt` |
| `scripts/run-probes.sh` | `output/03-matchers-*.txt`, `output/04-global-method-security-*.txt` |
| `scripts/compile-old-apis.sh` | `output/05-old-apis-*.txt`, `output/06-fixed-apis-*.txt`, `output/07-new-manager-*.txt` |
| `scripts/run-all.sh` | all of the above |
Needs JDK 17 or newer (built with 25), Maven 3.9, Python 3 and access to Maven Central. The `security6` and `security7`
Maven profiles pick Boot 3.5.16 + Security 6.5.11 or Boot 4.1.2 + Security 7.1.2.
`02-removed-api.txt` lists exact signatures that disappeared (generics and `throws` clauses are ignored). It is a list to
check, not a list of deletions: a method that moved to a superclass shows up as removed from the subclass.