From b0fc0abdcc27dcb8bad30e6d45622c81b36ca42b Mon Sep 17 00:00:00 2001 From: Fiona Date: Mon, 24 Aug 2026 01:53:01 -0700 Subject: [PATCH] ci: do not fail a release when the DingTalk notification fails The release workflow treated the DingTalk notification as a build gate: when the robot API rejects a message -- for example once its per-minute rate limit is exhausted -- the notification step failed and marked an otherwise successful publish as failed. Set `ignoreError` on every DingTalk step so a rejected notification is reported as a warning instead of failing the job. The publish outcome no longer depends on the notification channel. --- .github/workflows/publish-maven.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/publish-maven.yml b/.github/workflows/publish-maven.yml index 8d2906eea3..39862b1ec9 100644 --- a/.github/workflows/publish-maven.yml +++ b/.github/workflows/publish-maven.yml @@ -112,6 +112,7 @@ jobs: - name: Notify deployment success uses: zcong1993/actions-ding@master with: + ignoreError: "true" dingToken: ${{ secrets.DING_TALK_TOKEN }} secret: ${{ secrets.DING_TALK_SECRET }} body: | @@ -126,6 +127,7 @@ jobs: - name: Notify secondary DingTalk group on success uses: zcong1993/actions-ding@master with: + ignoreError: "true" dingToken: ${{ secrets.DING_TALK_TOKEN_2 }} secret: ${{ secrets.DING_TALK_SECRET_2 }} body: | @@ -159,6 +161,7 @@ jobs: - name: Notify deployment failure uses: zcong1993/actions-ding@master with: + ignoreError: "true" dingToken: ${{ secrets.DING_TALK_TOKEN }} secret: ${{ secrets.DING_TALK_SECRET }} body: |