mirror of
https://github.com/Tencent/BrowserSkill.git
synced 2026-09-10 13:01:23 +08:00
ci(dsh-plugin): publish from the npm-publish environment
The publish job named its GitHub Environment NPM_TOKEN, which is the secret name rather than a deployment target, so the repository's Deployments list showed a bogus NPM_TOKEN entry next to chrome-web-store. The environment is now npm-publish; the secret it holds keeps its name. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -66,8 +66,8 @@ jobs:
|
|||||||
publish:
|
publish:
|
||||||
needs: [resolve, guard]
|
needs: [resolve, guard]
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
# Secret NPM_TOKEN is stored on the GitHub Environment also named NPM_TOKEN.
|
# Secret NPM_TOKEN is stored on the "npm-publish" GitHub Environment.
|
||||||
environment: NPM_TOKEN
|
environment: npm-publish
|
||||||
permissions:
|
permissions:
|
||||||
contents: read
|
contents: read
|
||||||
steps:
|
steps:
|
||||||
|
|||||||
@@ -187,8 +187,8 @@ git tag dsh-plugin-v0.1.0
|
|||||||
git push origin dsh-plugin-v0.1.0
|
git push origin dsh-plugin-v0.1.0
|
||||||
```
|
```
|
||||||
|
|
||||||
Or run the workflow from the Actions tab (`workflow_dispatch`). The job reads
|
Or run the workflow from the Actions tab (`workflow_dispatch`). The job reads the
|
||||||
`NPM_TOKEN` from the GitHub Environment of the same name.
|
`NPM_TOKEN` secret from the `npm-publish` GitHub Environment.
|
||||||
|
|
||||||
## License
|
## License
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user