This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 07bf075b94f Update provider release doc to direct to security issues
board (#66769)
07bf075b94f is described below
commit 07bf075b94fb8679ac3f83b02c04226e5696fe0b
Author: Vincent <[email protected]>
AuthorDate: Tue May 12 11:08:54 2026 -0400
Update provider release doc to direct to security issues board (#66769)
---
dev/README_RELEASE_PROVIDERS.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev/README_RELEASE_PROVIDERS.md b/dev/README_RELEASE_PROVIDERS.md
index cac73e3e379..7064c2ae09f 100644
--- a/dev/README_RELEASE_PROVIDERS.md
+++ b/dev/README_RELEASE_PROVIDERS.md
@@ -1646,7 +1646,7 @@ Trying to send HTML content will result in failure.
## Send announcements about security issues fixed in the release
The release manager should review and mark as READY all the security issues
fixed in the release.
-Such issues can be listed under the `Next wave of providers` milestone in
[security
issues](https://github.com/airflow-s/airflow-s/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A%22Next%20wave%20of%20providers%22).
+Such issues can be listed under the section `Providers {RELEASE_DATE}` in
[security issues board](https://github.com/orgs/airflow-s/projects/2).
Go through the list of these issues and check for each of them the fix has
been released as part of this release.
Then the release manager should announce the issues via the CVE management
tool at https://cveprocess.apache.org/.
