Skip to content

Commit

Permalink
Set expiry date for the Security Policy (#1328)
Browse files Browse the repository at this point in the history
Include an expiry date in the security policy primarily as a mechanism
to ensure the supported version range can reasonable be updated if no
end-of-life date has yet been set for a version.

Additionally, it nudges anyone looking at the policy to search for an
up-to-date version - which is more helpful for anyone.
  • Loading branch information
ericcornelissen authored Apr 2, 2024
1 parent 36a3847 commit 6651227
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ appreciate your efforts to responsibly disclose your findings. Due to the
non-funded and open-source nature of the project, we take a best-efforts
approach when it comes to engaging with security reports.

This document should be considered expired after 2024-10-01. If you are
reading this after that date you should try to find an up-to-date version
in the official source repository.

## Supported Versions

The table below shows which versions of the project are currently supported
Expand Down

0 comments on commit 6651227

Please sign in to comment.