This is an automated email from the ASF dual-hosted git repository.
vincbeck pushed a commit to branch v3-2-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-2-test by this push:
new a2894103267 [v3-2-test] Update provider release doc to direct to
security issues board (#66769) (#66777)
a2894103267 is described below
commit a2894103267df55302e56584990e15f8b2ff57e2
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Tue May 12 12:00:44 2026 -0400
[v3-2-test] Update provider release doc to direct to security issues board
(#66769) (#66777)
(cherry picked from commit 07bf075b94fb8679ac3f83b02c04226e5696fe0b)
Co-authored-by: Vincent <[email protected]>
---
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 7aa3672ce3d..11a6df8c310 100644
--- a/dev/README_RELEASE_PROVIDERS.md
+++ b/dev/README_RELEASE_PROVIDERS.md
@@ -1635,7 +1635,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/.
