Skip to content

docs: bring SECURITY.md up to date - #197

Merged
willkg merged 1 commit into
mainfrom
security-md-95
Sep 25, 2026
Merged

willkg merged 1 commit into
mainfrom
security-md-95

Conversation

@willkg

@willkg willkg commented Sep 25, 2026

Copy link
Copy Markdown
Member

Closes #95.

#95 asked for three things. The support window was already decided (only the latest release is supported, with no backports before 1.0.0), and the version table stays deferred until there is more than one release line, as the file says. This PR settles the rest, and fixes two lines that had gone stale:

  • Token note: an Atlassian API token can't be edited or rotated in place, because Atlassian's UI only revokes one. So recovery means revoking it and issuing a new one. This is confirmed for personal tokens. Scoped service-account tokens are assumed to work the same way, since nobody here has access to check.
  • Image paths: described as bounded by the documentation root (the nearest markfluence.yaml, or the file's own directory), not the working directory, which has been out of date since the root model changed.
  • Report checklist: asks whether the site is standard Cloud or Government/isolated Cloud, not Cloud or Data Center, because Data Center is out of scope.

Closes #95. The support window was already decided (latest release only),
and the version table waits until there is more than one line; this
settles the rest:

- The token note says what was confirmed: Atlassian's UI offers no edit
  or rotation for a personal API token, only revocation. Scoped
  service-account tokens are assumed to behave the same; nobody here can
  check.
- Image paths are bounded by the documentation root, not the working
  directory, since the root model changed.
- A report asks about standard vs Government/isolated Cloud, not Data
  Center, which is out of scope.
@willkg
willkg merged commit 84b4363 into main Sep 25, 2026
1 check passed
@willkg
willkg deleted the security-md-95 branch September 25, 2026 12:05
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.

SECURITY.md: replace the no-releases-yet note with a supported-versions table

1 participant