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

leerho pushed a commit to branch update_stageReleaseSources
in repository https://gitbox.apache.org/repos/asf/datasketches-memory.git

commit 1e5b6ff52fde0fc3a6eaa101de46d5dd14756124
Author: Lee Rhodes <[email protected]>
AuthorDate: Tue Jun 9 13:55:40 2026 -0700

    Merge pull request #291 from apache/update_stageReleaseSources_action
    
    update stageReleaseSources.yml
---
 .github/workflows/stageReleaseSources.yml | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/stageReleaseSources.yml 
b/.github/workflows/stageReleaseSources.yml
index 16410b49..fc0d2e4f 100644
--- a/.github/workflows/stageReleaseSources.yml
+++ b/.github/workflows/stageReleaseSources.yml
@@ -1,8 +1,13 @@
 name: Stage Release Sources (Manual Trigger)
 
 # This workflow acts as Phase 1 of your official Release Candidate process.
-# It handles the clean compilation, license verification, and source packaging
-# on a cloud runner, delivering a pristine ZIP for local signing.
+# 1. It handles the clean compilation, license verification, and source 
packaging
+#    on a cloud runner, delivering a pristine ZIP for local signing.
+# 2. It computes the SHA512 checksum and attaches it as a file.
+# 3. It builds the project from just the source ZIP (no .git file) and runs 
all the unit tests
+#    on Windows, Ubuntu, and MacOS.
+# 4. Because we don't want to share private keys and credentials with this 
process, you will need
+#    to add the GPG .asc signature file before submitting the artifact to ASF.
 
 on:
   workflow_dispatch:
@@ -16,7 +21,7 @@ jobs:
     steps:
       # 1. Checkout the clean working workspace context
       - name: 1. Checkout Branch Context
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           ref: ${{ github.ref }}
           fetch-depth: 0


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to