Skip to content

Commit fb333e0

Browse files
TMHSDigitalclaude
andcommitted
fix: state the current security support policy
The supported-versions table named 0.2.x while the repository is at 0.78.18, so it claimed support for releases eleven minors behind and none of the ones that exist. Replace it with the policy the project can actually keep: latest release only, no backports, no maintenance branches. The row points at VERSION rather than naming a number, so it cannot drift again on the next release. Adds the one-line reason there are no backports — this is content, not a runtime. Closes #186 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: TMHSDigital <154358121+TMHSDigital@users.noreply.github.com>
1 parent 6440e83 commit fb333e0

1 file changed

Lines changed: 11 additions & 2 deletions

File tree

‎SECURITY.md‎

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,10 +26,19 @@ Issues with the Blender Python API itself (`bpy`, `bmesh`, `bpy_extras`) belong
2626

2727
## Supported Versions
2828

29+
This is a content repository — Markdown, MDC, Python, and TOML files consumed
30+
directly by an AI agent. There is no installed runtime, no server, and no
31+
long-lived deployment to patch, so there are no maintenance branches and no
32+
backports.
33+
2934
| Version | Supported |
3035
|---------|-----------|
31-
| 0.2.x | Yes |
32-
| < 0.2.0 | No |
36+
| Latest release (see [`VERSION`](VERSION)) | Yes |
37+
| Any earlier release | No |
38+
39+
A confirmed fix lands on `main` and ships in the next release cut by
40+
`release.yml`. Consumers pin by tag or track `main`; the remedy in both cases
41+
is to move to the current release. Nothing older is patched in place.
3342

3443
## Response Timeline
3544

0 commit comments

Comments
 (0)