(superset) branch fix_release_tags updated (3522724a40 -> 057ab351f2)

[ma...@apache.org]

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

maximebeauchemin pushed a change to branch fix_release_tags
in repository https://gitbox.apache.org/repos/asf/superset.git


 discard 3522724a40 fix(ci): release process for labeling PRs
     new 057ab351f2 fix(ci): release process for labeling PRs

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (3522724a40)
            \
             N -- N -- N   refs/heads/fix_release_tags (057ab351f2)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .github/workflows/tag-release.yml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

(superset) 01/01: fix(ci): release process for labeling PRs

[ma...@apache.org]

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

maximebeauchemin pushed a commit to branch fix_release_tags
in repository https://gitbox.apache.org/repos/asf/superset.git

commit 057ab351f2d4428a7a088e82a66fd0ecc8427920
Author: Maxime Beauchemin <ma...@gmail.com>
AuthorDate: Wed Jul 24 12:38:24 2024 -0700

    fix(ci): release process for labeling PRs
    
    It appears the CI script that runs on-release to label PRs isn't working
    as expected. Here I'm taking the `supersetbot` command out of the matrix
    and running it in parallel with the docker image publication.
    
    Tested with:
    ```
    gh workflow run tag-release.yml --ref fix_release_tags --field
    release="4.0.2" --field git-ref="4.0.2" --field force-latest="true"
    ```
    
    Test run:
---
 .github/workflows/tag-release.yml | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/tag-release.yml b/.github/workflows/tag-release.yml
index 8ee03b3d04..df1bd3cc06 100644
--- a/.github/workflows/tag-release.yml
+++ b/.github/workflows/tag-release.yml
@@ -58,9 +58,6 @@ jobs:
           tags: true
           fetch-depth: 0
 
-      - name: Setup supersetbot
-        uses: ./.github/actions/setup-supersetbot/
-
       - name: Try to login to DockerHub
         continue-on-error: true
         uses: docker/login-action@v3
@@ -94,7 +91,15 @@ jobs:
             --platform "linux/arm64" \
             --platform "linux/amd64"
 
-      # Going back on original branch to allow "post" GHA operations
+  update-prs-with-release-info:
+    needs: config
+    if: needs.config.outputs.has-secrets
+    runs-on: ubuntu-22.04
+    steps:
+
+      - name: Setup supersetbot
+        uses: ./.github/actions/setup-supersetbot/
+
       - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
         uses: actions/checkout@v4
         with: