Skip to content

Commit ca09603

Browse files
committed
Fix release workflow
Environment variables written to GITHUB_ENV are not available in the 'env' context until next step. So within the "Set release version" step we use plain environment variables instead of accessing the 'env' context.
1 parent c496f44 commit ca09603

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

.github/workflows/release.yml

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,14 @@ jobs:
2424
2525
- name: Set release version
2626
run: |
27-
echo "VERSION_NUMBER=$(./setup.py --version)" >> $GITHUB_ENV
28-
echo "NEXT_VERSION_NUMBER=$(echo ${{ env.VERSION_NUMBER }} | awk -F. -v OFS=. '{$2 += 1 ; print}')" >> $GITHUB_ENV
29-
echo Next version number: ${{ env.NEXT_VERSION_NUMBER }}
30-
sed -i 's/${{ env.VERSION_NUMBER }}/${{ env.NEXT_VERSION_NUMBER }}/' trino/__init__.py
27+
VERSION_NUMBER="$(./setup.py --version)"
28+
NEXT_VERSION_NUMBER="$(echo ${VERSION_NUMBER} | awk -F. -v OFS=. '{$2 += 1 ; print}')"
29+
echo "Current version: ${VERSION_NUMBER}; Next version number: ${NEXT_VERSION_NUMBER}"
30+
sed -i "s/${VERSION_NUMBER}/${NEXT_VERSION_NUMBER}/g" trino/__init__.py
31+
32+
# Export for use in next steps
33+
echo "VERSION_NUMBER=${VERSION_NUMBER}" >> $GITHUB_ENV
34+
echo "NEXT_VERSION_NUMBER=${NEXT_VERSION_NUMBER}" >> $GITHUB_ENV
3135
3236
- name: Prepare release
3337
run: |

0 commit comments

Comments
 (0)