MB683 is a small but important public-security metadata round.
The repository’s public security policy had drifted behind the actual supported release lines. GitHub’s .github/SECURITY.md still referred to older version families while the project had already moved forward.
The final commit is:
Version : 3.4dev-20260822_071847
Commit : eb6f855
Branch : master
🛡️ Keep the Security Scroll in Sync With the Current Spellbook
MB683 is intentionally narrow.
It changes only:
.github/SECURITY.md
VERSION
t/cases/885_mb683_security_policy_version_sync.t
No runtime code changed.
No updater code changed.
No installer changed.
No database or schema changed.
Before MB683, the public GitHub security policy still advertised outdated support lines:
3.1 stable
3.2-dev
while the public repository had already moved to:
3.3 stable
3.4dev active development
That matters because .github/SECURITY.md is the page contributors and security reporters may consult before submitting a vulnerability report.
An obsolete support matrix there is not merely cosmetic documentation drift.
The policy now reflects the actual public version lines:
stable : 3.3
development : 3.4dev
The existing private vulnerability-reporting guidance is preserved.
The existing warning against publishing secrets or sensitive information in public issues is also preserved.
MB683 adds:
t/cases/885_mb683_security_policy_version_sync.t
The test prevents the public security policy from silently drifting away from the version information documented elsewhere in the repository.
This turns the support matrix from a manually maintained convention into a regression-checked public contract.
The expanded release/security/documentation group covered:
662
682
716
718
721
723
884
885
Result:
PASSED : 172/172 (1s)
The MB683-specific contract itself passed:
PASSED : 10/10
perl t/test_commands.pl --fast --progress
Result:
Selected: 324 of 768 discovered test file(s)
[====================] 100% [324/324 files | 5992 tests]
PASSED : 5992/5992 (65s)
perl t/test_commands.pl --progress
Result:
[====================] 100% [768/768 files | 15465 tests]
PASSED : 15465/15465 (212s)
Because the round contains no runtime change, no service restart was required.
The final worktree guard confirmed:
OK: no runtime/product file modified
Before commit, the only project changes were:
M .github/SECURITY.md
A t/cases/885_mb683_security_policy_version_sync.t
plus the automatic VERSION update during commit.
Version : 3.4dev-20260822_071847
Commit : eb6f855
🛡️ Keep the Security Scroll in Sync With the Current Spellbook
Commit summary:
3 files changed
86 insertions
3 deletions
New test:
t/cases/885_mb683_security_policy_version_sync.t
The commit was successfully pushed to GitHub.
Security reporting starts before anyone reads the code.
The public security policy should therefore be just as trustworthy as the runtime documentation.
MB683 makes that version support statement explicit and test-backed.
MB683 closes the small public-policy drift found after MB682.
The next round should return to substantive 3.5 readiness work.
The likely next axis is:
Debian 13
fresh installation
installation prerequisites
configure/bootstrap assumptions
first-start validation
But the exact MB684 scope must still be derived from a fresh post-eb6f855 snapshot.
🛡️ A security scroll is only useful if it names the castle that actually exists.
You must be logged in to reply.