Skip to content

Commit bc49213

Browse files
committed
clarify the release schedule responsibility better
1 parent d59b9b6 commit bc49213

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

SECURITY.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,6 @@ CVEs for the base operating system image packages should be reported to those re
1313

1414
When base images are patched, the images are rebuilt and rolled out to the Docker hub without intervention by this repo. This process is explained in <https://github.com/docker-library/faq/#why-does-my-security-scanner-show-that-an-image-has-cves>.
1515

16-
When vulnerabilities are resolved in a Node.js release, they are routinely released in a corresponding new Node.js Docker image from time to time as needed.
16+
When vulnerabilities are resolved in a Node.js release, they are routinely released in a corresponding new Node.js Docker image. The schedule is determined by the Node.js releases not by the Node.js Docker repo.
1717

1818
Please do not open issues in this repo for vulnerabilities in the above components. If they cannot be actioned here, the issue will be closed.

0 commit comments

Comments
 (0)