Repository navigation
docs(skills): carry the 7.4.0 / 6.12.0 advisory lessons into the release skills - #1987
Merged
Merged
Conversation
…ase skills Four baseline scenarios run against the previous skills, with project memory off-limits, each failed: - Friday publication: no skill held advisories over a weekend; the rule existed only in memory. - Version Notes after publication: "the notes may link it" led to inline bulletin links in the type sections, no Security section. - CVE record: nothing on the record's fields, so ranges were merged across lines and the title double-prefixed. - After the mails: nothing past the send button; reporter notices, the site PR and the THREAT_MODEL.md section 12 check went unmentioned. creating-security-bulletins gains a publication-day rule, a "Filling the CVE record" section (house JSON shape: one range per bulletin line, Maven purl, text severity with the GENERAL scenario, four-part description, JSON-editor write path, READY as the PMC's last step) and an "After the advisory mails" checklist. creating-version-notes defines the Security section, its place and its line format. releasing-struts updates the phase 7 gate and the publication ordering. The same four scenarios rerun against these edits all pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Folds what the 7.4.0 / 6.12.0 advisory round (S2-075 … S2-078) taught into the three release skills.
How the gaps were found
Four scenarios were run against the skills on
main, with project memory off-limits so only the skills were tested. Each failed:mainApache Struts:THREAT_MODEL.md§12 re-baseline check went unmentionedThe same four scenarios rerun against this branch all pass, and the CVE-record and Version Notes outputs match what was actually published for S2-075 … S2-078.
Changes
creating-security-bulletinsREADYor send on a Friday or before a holiday; prepare and propose Monday.versionsentry per bulletin line, MavenpackageURL, text severity with theGENERALscenario, four-part description, CWE chosen and named to the release manager), the JSON-editor write path, andREADYas the PMC's last step.Securitysection, site PR, one reporter notice per report thread, the threat-model check.creating-version-notes— theSecuritysection: placement after Maven users, line format, and the section-update write path; section order, checklist and red flags updated.releasing-struts— phase 7 gate names the working-day rule and the follow-ups; the ordering states that ASF Security pushes to MITRE.🤖 Generated with Claude Code