Use NAPCAT_BUILD secret for release

Switch the release workflow to use the NAPCAT_BUILD secret instead of the default GITHUB_TOKEN. This allows the release job to run with a dedicated token (e.g., with different scopes or credentials) when creating tags, changelogs, and uploading release artifacts.
2026-03-05 09:16:46 +08:00
parent 66542eda26
commit 776cc8cefd
1 changed files with 1 additions and 1 deletions
@@ -440,7 +440,7 @@ jobs:
        with:
          tag_name: ${{ github.ref_name }}
          name: NapCat ${{ github.ref_name }}
-          token: ${{ secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.NAPCAT_BUILD }}
          body_path: CHANGELOG.md
          files: |
            NapCat.Shell.Windows.Node.zip