📝 update readme

Author: ctcpip

README.md

@@ -22,20 +22,30 @@ In some cases, it may be unavoidable that a security fix involves a breaking cha
 
 ## Acceptance criteria for patched releases
 
-- Wherever possible, reuse the existing patch code from patched jQuery releases
-- All existing passing tests must pass
+- All CVEs for the release MUST be patched
+- Wherever possible, reuse the existing patch code from patched official jQuery releases
+- All existing passing tests MUST pass
 - Additional unit/integration test coverage as needed to account for the changes
 - A/B end-to-end acceptance tests against the unpatched and patched versions for all CVEs
 
-## Available patched releases
+## Patched releases
+
+In a perfect world, at least every MAJOR EOL jQuery release line would have a security-patched release. "Major" refers to the meaning of the term in [SemVer](https://semver.org/), thus releases that have breaking changes. The goal is to provide a patched version of jQuery for all major release lines to provide a path of least resistance for all downstream users to upgrade to a secure version jQuery with [no (or minimal) breaking changes](#but-what-about-breaking-changes).
 
 | jQuery version | jQuery-sec version | Branch                    | PR             | Release |
 | -------------- | ------------------ | ------------------------- | -------------- | ------- |
-| 1.6.4          | 1.6.5-sec          | [1.6.5-sec][1.6.5-branch] | [PR][1.6.5-pr] | TODO    |
-
-### Future releases
-
-In a perfect world, at least every MAJOR jQuery release line would have a security-patched release. "Major" refers to the meaning of the term in [SemVer](https://semver.org/), thus releases that have breaking changes. The goal is to provide a patched version of jQuery for all major release lines to provide a path of least resistance for all downstream users to upgrade to a secure version jQuery with [no (or minimal) breaking changes](#but-what-about-breaking-changes).
+| `1.2.6`        | `1.2.7-sec`        |                           |                |         |
+| `1.3.2`        | `1.3.3-sec`        |                           |                |         |
+| `1.4.4`        | `1.4.5-sec`        |                           |                |         |
+| `1.5.2`        | `1.5.3-sec`        |                           |                |         |
+| `1.6.4`        | `1.6.5-sec`        | [1.6.5-sec][1.6.5-branch] | [PR][1.6.5-pr] | TODO    |
+| `1.7.2`        | `1.7.3-sec`        |                           |                |         |
+| `1.8.3`        | `1.8.4-sec`        |                           |                |         |
+| `1.12.4`       | `1.12.5-sec`       |                           |                |         |
+| `2.2.4`        | `2.2.5-sec`        |                           |                |         |
+
+> [!NOTE]
+> The 3.x release line is currently supported by jQuery, so we have no need to provide patched versions of 3.x at this time. jQuery 3.5 introduced a breaking change, but it was necessary to fix CVE-2020-11022 and CVE-2020-11023. However, since these vulnerabilities are present in virtually all versions of jQuery, there would be no value in providing a patched version of 3.4 as it would need to include that breaking change anyway.
 
 ## Goals