(opendal) branch main updated: docs(release): fix CI workflow links for bindings (#6437)

[as...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

asukaminato pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/opendal.git


The following commit(s) were added to refs/heads/main by this push:
     new 8de30cc76 docs(release): fix CI workflow links for bindings (#6437)
8de30cc76 is described below

commit 8de30cc764c3724db33907ca17e02648530061ed
Author: Kingsword <ki...@gmail.com>
AuthorDate: Mon Jul 21 00:44:15 2025 +0800

    docs(release): fix CI workflow links for bindings (#6437)
---
 website/community/release/release.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/community/release/release.md b/website/community/release/release.md
index 554f970fc..9a1187b03 100644
--- a/website/community/release/release.md
+++ b/website/community/release/release.md
@@ -119,9 +119,9 @@ Pushing a Git tag to GitHub repo will trigger a GitHub Actions workflow that cre
 
 After pushing the tag, we need to check the GitHub action status to make sure the release candidate is created successfully.
 
-- Python: [Bindings Python CI](https://github.com/apache/opendal/actions/workflows/bindings_python.yml)
-- Java: [Bindings Java CI](https://github.com/apache/opendal/actions/workflows/bindings_java.yml) and [Bindings Java Release](https://github.com/apache/opendal/actions/workflows/release_java.yml)
-- Node.js: [Bindings Node.js CI](https://github.com/apache/opendal/actions/workflows/bindings_nodejs.yml)
+- Python: [Bindings Python CI](https://github.com/apache/opendal/actions/workflows/ci_bindings_python.yml)
+- Java: [Bindings Java CI](https://github.com/apache/opendal/actions/workflows/ci_bindings_java.yml) and [Bindings Java Release](https://github.com/apache/opendal/actions/workflows/release_java.yml)
+- Node.js: [Bindings Node.js CI](https://github.com/apache/opendal/actions/workflows/ci_bindings_nodejs.yml)
 
 In the most cases, it would be great to rerun the failed workflow directly when you find some failures. But if a new code patch is needed to fix the failure, you should create a new release candidate tag, increase the rc number and push it to GitHub.