fix : use REGISTRY_TOKEN instead of RELEASE_TOKEN in CI workflows
Some checks failed
Auto Tag Develop / tag (push) Has been cancelled
Some checks failed
Auto Tag Develop / tag (push) Has been cancelled
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -13,7 +13,7 @@ jobs:
|
|||||||
uses: actions/checkout@v4
|
uses: actions/checkout@v4
|
||||||
with:
|
with:
|
||||||
fetch-depth: 0
|
fetch-depth: 0
|
||||||
token: ${{ secrets.RELEASE_TOKEN }}
|
token: ${{ secrets.REGISTRY_TOKEN }}
|
||||||
persist-credentials: true
|
persist-credentials: true
|
||||||
|
|
||||||
- name: Create next tag from VERSION
|
- name: Create next tag from VERSION
|
||||||
|
|||||||
@@ -64,4 +64,4 @@ jobs:
|
|||||||
with:
|
with:
|
||||||
files: release/inventory-${{ github.ref_name }}.tar.gz
|
files: release/inventory-${{ github.ref_name }}.tar.gz
|
||||||
env:
|
env:
|
||||||
GITHUB_TOKEN: ${{ secrets.RELEASE_TOKEN }}
|
GITHUB_TOKEN: ${{ secrets.REGISTRY_TOKEN }}
|
||||||
|
|||||||
Reference in New Issue
Block a user