refactor: streamline GPG key handling in release workflow

This commit is contained in:
arashagp
2025-01-02 11:23:29 +03:30
parent 1f8ffd2f69
commit ef28694385

View File

@@ -24,9 +24,6 @@ on:
permissions: permissions:
contents: write contents: write
env:
GPG_PRIVATE_KEY: ${{ secrets.GPG_PRIVATE_KEY }}
jobs: jobs:
main: main:
name: Build & Lint & Test & Release name: Build & Lint & Test & Release
@@ -45,6 +42,7 @@ jobs:
echo -e "5\ny\n" | gpg --batch --yes --command-fd 0 --edit-key ${{ secrets.GPG_KEY_ID }} trust quit echo -e "5\ny\n" | gpg --batch --yes --command-fd 0 --edit-key ${{ secrets.GPG_KEY_ID }} trust quit
env: env:
GPG_PRIVATE_KEY: ${{ secrets.GPG_PRIVATE_KEY}} GPG_PRIVATE_KEY: ${{ secrets.GPG_PRIVATE_KEY}}
GPG_KEY_ID: ${{ secrets.GPG_KEY_ID }}
- name: 🫡 Setup Git - name: 🫡 Setup Git
run: | run: |
@@ -52,6 +50,8 @@ jobs:
git config --global user.email "bot@thenexim.com" git config --global user.email "bot@thenexim.com"
git config --global user.signingkey ${{ secrets.GPG_KEY_ID }} git config --global user.signingkey ${{ secrets.GPG_KEY_ID }}
git config --global commit.gpgsign true git config --global commit.gpgsign true
env:
GPG_KEY_ID: ${{ secrets.GPG_KEY_ID }}
- name: 🔧 Setup Node.js - name: 🔧 Setup Node.js
uses: actions/setup-node@v4 uses: actions/setup-node@v4