Compare commits
12
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
4bddb37de2 | ||
|
|
aa90774738 | ||
|
|
d7e14f6d02 | ||
|
|
4a943a5651 | ||
|
|
f47a5102d6 | ||
|
|
05596bce72 | ||
|
|
c6e84efc28 | ||
|
|
0cbe8046af | ||
|
|
ea32d10fa6 | ||
|
|
deb1b7f9cb | ||
|
|
2d7f607649 | ||
|
|
91eae117ed |
@@ -7,13 +7,14 @@ name: Release
|
||||
- beta
|
||||
- "*.x"
|
||||
permissions:
|
||||
contents: read # for checkout
|
||||
contents: read # for checkout
|
||||
jobs:
|
||||
release:
|
||||
permissions:
|
||||
contents: write # to be able to publish a GitHub release
|
||||
issues: write # to be able to comment on released issues
|
||||
pull-requests: write # to be able to comment on released pull requests
|
||||
contents: write # to be able to publish a GitHub release
|
||||
issues: write # to be able to comment on released issues
|
||||
pull-requests: write # to be able to comment on released pull requests
|
||||
id-token: write # to enable use of OIDC for npm provenance
|
||||
name: release
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
|
||||
@@ -158,14 +158,6 @@ Or with the `publishConfig.access` key in your project's `package.json`:
|
||||
}
|
||||
```
|
||||
|
||||
## Can I use semantic-release to publish a package on Artifactory?
|
||||
|
||||
Any npm compatible registry is supported with the [`@semantic-release/npm`](https://github.com/semantic-release/npm) plugin. For Artifactory versions prior to 5.4, the legacy authentication has to be used (with `NPM_USERNAME`, `NPM_PASSWORD` and `NPM_EMAIL` [environment variables](https://github.com/semantic-release/npm#environment-variables)).
|
||||
|
||||
See [npm registry authentication](https://github.com/semantic-release/npm#npm-registry-authentication) for more details.
|
||||
|
||||
See [Artifactory - npm Registry](https://www.jfrog.com/confluence/display/RTF/Npm+Registry#NpmRegistry-AuthenticatingthenpmClient) documentation for Artifactory configuration.
|
||||
|
||||
## Can I manually trigger the release of a specific version?
|
||||
|
||||
You can trigger a release by pushing to your Git repository. You deliberately cannot trigger a _specific_ version release, because this is the whole point of semantic-release.
|
||||
|
||||
Generated
+472
-5148
File diff suppressed because it is too large
Load Diff
+11
-10
@@ -34,7 +34,7 @@
|
||||
"aggregate-error": "^4.0.1",
|
||||
"cosmiconfig": "^8.0.0",
|
||||
"debug": "^4.0.0",
|
||||
"env-ci": "^8.0.0",
|
||||
"env-ci": "^9.0.0",
|
||||
"execa": "^7.0.0",
|
||||
"figures": "^5.0.0",
|
||||
"find-versions": "^5.1.0",
|
||||
@@ -62,18 +62,18 @@
|
||||
"codecov": "3.8.3",
|
||||
"delay": "5.0.0",
|
||||
"dockerode": "3.3.5",
|
||||
"file-url": "^4.0.0",
|
||||
"fs-extra": "^11.0.0",
|
||||
"got": "^12.5.0",
|
||||
"file-url": "4.0.0",
|
||||
"fs-extra": "11.1.1",
|
||||
"got": "12.6.0",
|
||||
"js-yaml": "4.1.0",
|
||||
"mockserver-client": "5.15.0",
|
||||
"nock": "13.3.0",
|
||||
"p-retry": "^5.1.1",
|
||||
"prettier": "^2.7.1",
|
||||
"sinon": "15.0.2",
|
||||
"p-retry": "5.1.2",
|
||||
"prettier": "2.8.7",
|
||||
"sinon": "15.0.3",
|
||||
"stream-buffers": "3.0.2",
|
||||
"tempy": "^3.0.0",
|
||||
"testdouble": "3.17.0"
|
||||
"tempy": "3.0.0",
|
||||
"testdouble": "3.17.2"
|
||||
},
|
||||
"engines": {
|
||||
"node": ">=18"
|
||||
@@ -117,7 +117,8 @@
|
||||
"trailingComma": "es5"
|
||||
},
|
||||
"publishConfig": {
|
||||
"access": "public"
|
||||
"access": "public",
|
||||
"provenance": true
|
||||
},
|
||||
"repository": {
|
||||
"type": "git",
|
||||
|
||||
Reference in New Issue
Block a user