semantic-release / github Goto Github PK
View Code? Open in Web Editor NEW:octocat: semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues
License: MIT License
:octocat: semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues
License: MIT License
Branch | Build failing π¨ |
---|---|
Dependency |
@octokit/rest
|
Current Version | 15.4.1 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 14 commits.
c1fc675
fix: workaround for github.activity.markNotificationsAsRead() (#694)
935c55c
test: mark notifications as read
be0be42
test: correctly authenticate as app
2f11117
refactor: remove obsolete application/vnd.github.machine-man-preview
default header, it gets added automatically when authenticating as an app
09e3c46
fix: amend accept header for github apps, keep custom accept headers intact
c614739
test: add machine preview header when authenticated as apps
96a2f95
fix(routes): default header for checks APIs
5c3d5a0
test: set default header for new checks API
cde9ac2
test: custom headers are case insensitive
4eb46d8
test: case-insensitive accept header for #861
b56f0d2
feat: authentication type "app". "integration" is now deprecated
2aa238b
test: adapt app authentication test
c2371ba
deprecate: authentication type "integration"
726bf35
test: deprecate authentication type "integration"
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Doing a first release resulted in the following success comment being added to two merged PRs:
π This PR is included in version 1.0.0 π
The release is available on:
v1.0.0
- GitHub release
v1.0.0
Your semantic-release bot π¦π
Versions in use:
"semantic-release": ">=16.0.0-beta <17.0.0",
"@semantic-release/commit-analyzer": ">=7.0.0-beta <8.0.0",
"@semantic-release/release-notes-generator": "^7.1.4",
"@semantic-release/changelog": "^3.0.1",
"@semantic-release/exec": ">=3.3.0-beta <4.0.0",
"@semantic-release/git": ">=7.1.0-beta <8.0.0",
"@semantic-release/npm": ">=5.2.0-beta <6.0.0",
"@semantic-release/github": ">=5.3.0-beta <6.0.0"
Configuration used:
"release": {
"branches": [
"+([1-9])?(.{+([1-9]),x}).x",
"latest",
"master",
"next",
"next-major",
{"name": "prerelease", "prerelease": "prerelease"},
{"name": "beta", "prerelease": "beta"},
{"name": "alpha", "prerelease": "alpha"}
],
"plugins": [
["@semantic-release/commit-analyzer", {
"parserOpts": {
"revertPattern": "/^(?:Revert|revert:)\\s\"?([\\s\\S]+?)\"?\\s*This reverts commit (\\w*)\\./"
},
"releaseRules": "./release-rules.js"
}],
["@semantic-release/release-notes-generator", {
"parserOpts": {
"revertPattern": "/^(?:Revert|revert:)\\s\"?([\\s\\S]+?)\"?\\s*This reverts commit (\\w*)\\./"
}
}],
["@semantic-release/changelog", {
"changelogFile": "./CHANGELOG.md"
}],
["@semantic-release/npm", {
"tarballDir": "./npm"
}],
["@semantic-release/git", {
"message": "chore(release): set version to ${nextRelease.version}\n\n${nextRelease.notes}",
"assets": [
"../../../CHANGELOG.md",
"../../Package/package.json"
]
}],
["@semantic-release/github", {
"assets": [
{"path": "./npm", "label": "Package"}
]
}],
["@semantic-release/exec", {
"successCmd": "./some-script.sh"
}]
]
}
Note that I'm also using
"private": true
in the package.json
, so the npm
plugin is actually not publishing - it's released on GitHub instead.
I tried finding the root of this but can't - I think it has to do with each plugin being able to return release information in the success
step?
Thanks a lot for the hard work, semantic-release
is an invaluable tool!
while npm pack
shows expected list of files, when i do release the package contains all the files from the project including those mentioned in .npmignore
dependencies:
"@semantic-release/changelog": "^3.0.0",
"@semantic-release/commit-analyzer": "^6.0.0",
"@semantic-release/git": "^7.0.1",
"@semantic-release/github": "^5.0.1",
"@semantic-release/release-notes-generator": "^7.0.0",
"semantic-release": "^15.8.1"
my .releaserc.json
:
{
"branch": "master",
"debug": true,
"noCi": true,
"npmPublish": false,
"githubUrl": "...",
"githubApiPathPrefix": "...",
"repository": {
"type": "git",
"url": "..."
},
"verifyConditions": [
"@semantic-release/changelog",
"@semantic-release/github"
],
"getLastRelease": "@semantic-release/git",
"prepare": [
{
"path": "@semantic-release/git",
"assets": [
"package.json",
"CHANGELOG.md"
],
"message": "chore(release): releasing ${nextRelease.version}\n\n${nextRelease.notes}"
}
],
"publish": [
{
"path": "@semantic-release/github",
"assets": [
"package.json",
"CHANGELOG.md"
]
}
]
}
if .npmignore
is not the right file to filter out things that are added to the package, how else can i do that? i also tried files: [ ... ]
in package.json
- also does not help
Branch | Build failing π¨ |
---|---|
Dependency |
semantic-release
|
Current Version | 15.4.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
git rev-parse origin/${branch}
to verify origin head (d7081fa)The new version differs by 1 commits.
d7081fa
fix: use git rev-parse origin/${branch}
to verify origin head
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency |
bottleneck
|
Current Version | 2.3.1 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
bottleneck is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
After the success
plugin was added, semantic-release
posts (or attempts to) a comment to every single PR in the entire repository. I assumed this isn't the intended behavior, but it's not clear to me why this is happening? What are the criteria used to identify eligible PRs?
I have an enterprise github setup which is behind a proxy. Octokit
supports this configuration but there is no notion to pass proxy configuration in @sementic-release/github
library.
Am I missing something?
I have tested this by changing the Octokit
initialization in the following line (It works!):
https://github.com/semantic-release/github/blob/master/lib/get-client.js#L105
Branch | Build failing π¨ |
---|---|
Dependency |
@octokit/rest
|
Current Version | 15.4.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 15 commits.
72bd9af
fix(validate): default to empty member array if optional parent parameter is not set
2a69a3a
fix(validate): default to empty member array if optional parent parameter is not set
8ad8919
build: routes
b665a2b
chore(package): update @octokit/routes to version 7.2.6
d29eb23
chore(package): update @octokit/routes to version 7.2.5
ef9dd1e
ci(travis): fix syntax
b716c30
build: routes
23510d8
chore(package): update @octokit/routes to version 7.2.4
def5bca
ci(travis): donβt fail if the greenkeeper script does not emit any changes
46d2396
ci(travis): donβt fail if the greenkeeper script does not emit any changes
4a227b4
ci(travis): set author when commiting changes in greenkeeper script
a398df4
ci(travis): adapt greenkeeper script for routes updates
65c3a29
build: routes
beef653
chore(package): update @octokit/routes to version 7.2.3
3aa8901
ci(travis): fix git push command for greenkeeper-routes-update
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | github |
Current Version | 12.0.3 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
github is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 2 commits.
1667120
fix(package): update follow-redirects to version 1.2.6
309e66e
docs(README): fixlink to promise example (#651)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | prettier |
Current Version | 1.9.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Octokit was upgraded from 15 to 16 in a patch version (https://github.com/semantic-release/github/releases/tag/v5.2.2), which has broken our GHE environment. According to this PR, it's an unintended side-effect (https://github.com/octokit/rest.js/issues/1127).
Not sure of the best approach here, but maybe major version bumps should coincide with a major release.
Hi,
I get following errors during running semantic-release version 15.13.3 in Travis CI. Who can help me to fix it. Thanks in advance.
[2:12:43 PM] [semantic-release] [@semantic-release/github] βΊ βΉ Verify GitHub authentication
Error: octokit.authenticate() is deprecated. Use "auth" constructor option instead.
at authenticate (/home/travis/build/bndynet/bbootstrap/node_modules/@octokit/rest/plugins/authentication-deprecated/authenticate.js:4:16)
at module.exports (/home/travis/build/bndynet/bbootstrap/node_modules/@semantic-release/github/lib/get-client.js:59:10)
at module.exports (/home/travis/build/bndynet/bbootstrap/node_modules/@semantic-release/github/lib/verify.js:53:20)
at verifyConditions (/home/travis/build/bndynet/bbootstrap/node_modules/@semantic-release/github/index.js:24:9)
at validator (/home/travis/build/bndynet/bbootstrap/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
at pReduce (/home/travis/build/bndynet/bbootstrap/node_modules/semantic-release/lib/plugins/pipeline.js:37:40)
at Promise.all.then.value (/home/travis/build/bndynet/bbootstrap/node_modules/p-reduce/index.js:16:10)
at process._tickCallback (internal/process/next_tick.js:68:7)
15.15.1
to 15.16.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
+json
format to preview accept headers (4302523)client.teams.addMember
, client.teams.addOrUpdateProject
, client.teams.createDiscussionComment
, client.teams.createDiscussion
, client.teams.deleteDiscussionComment
, client.teams.deleteDiscussion
, client.teams.getDiscussionComment
, client.teams.getDiscussion
, client.teams.getMember
, client.teams.listDiscussionComments
, client.teams.listDiscussions
, client.teams.listProjects
, client.teams.removeMember
, client.teams.removeProject
, client.teams.reviewProject
, client.teams.updateDiscussionComment
, client.teams.updateDiscussion
(3ec71cb)The new version differs by 5 commits.
3ec71cb
feat: client.teams.addMember
, client.teams.addOrUpdateProject
, client.teams.createDiscussionComment
, client.teams.createDiscussion
, client.teams.deleteDiscussionComment
, client.teams.deleteDiscussion
, client.teams.getDiscussionComment
, client.teams.getDiscussion
, client.teams.getMember
, client.teams.listDiscussionComments
, client.teams.listDiscussions
, client.teams.listProjects
, client.teams.removeMember
, client.teams.removeProject
, client.teams.reviewProject
, client.teams.updateDiscussionComment
, client.teams.updateDiscussion
47d31e9
feat: .repos.updateInformationAboutPagesSite()
6c9d410
deprecate: add deprecation flag to aliases output.annotations[].filename
, output.annotations[].warning_level
, id
alias for {project,column,card}_id
, contentLength
, contentType
4302523
fix(routes): add +json
format to preview accept headers
33aba5d
refactor: remove obsolete file
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
I've run into a couple of situations where I'm bumping a few libraries quickly enough that I seem to hit the github API rate limit by the time semantic-release needs to do its thing. The current mode of failure is
Once I'm in this state, someone usually comes up to me and tells me that no release was cut.
I think that a rate limit error should fail the build, so that when the github account comes out of the rate limit window, it can be manually restarted to attempt the same release again.
As it stands, I end up waiting for a half hour and making a trivial commit of some sort in order to trigger a new patch release.
Branch | Build failing π¨ |
---|---|
Dependency | github |
Current Version | 12.0.6 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
github is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 3 commits.
1e07daf
fix: whitelist X-GitHub-SSO header in response (#663)
d5a3261
chore(package): @octokit/fixtures^5.4.0
081d5a0
test(scenario): search issues
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency |
@octokit/rest
|
Current Version | 15.7.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
repository_id
parameter is required for .search.labels()
(b7e3add)The new version differs by 20 commits.
347b59d
refactor: response.meta
-> response.headers
5bf104c
feat: response.status
7ec8a03
feat: response.headers
(deprecates response.meta
)
244c7bf
build: adapt typescript definitions for response.headers & response.data
8c38374
docs(README): show response status & headers in code examples
6b0f254
test: response.headers
and response.status
e386e7a
test: adopt for deprecated parameter names
6584e60
build: routes for API docs
c62b2bc
deprecate: id
parameter renamed to <resource>_id
for several methods
59207cc
deprecate: oldname
parameter renamed to current_name
for .issues.updateLabel()
79925a1
feat: actions{}
parameter added to .checks.create()
and .checks.update()
b7e3add
fix: repository_id
parameter is required for .search.labels()
a1b5242
refactor: deviate deprecation message from alias
82e6907
build(generate-routes): adapt from scope name change (migration
-> migrations
)
3283733
build(package): update @octokit/routes to version 8.0.1
There are 20 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Is there a way to publish as github pre-release? I couldn't find any setting unfortunately.
Thank you! L~
Branch | Build failing π¨ |
---|---|
Dependency | debug |
Current Version | 4.0.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
debug is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
This patch restores browserify functionality as well as keeping the intended functionality with Unpkg.com.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Are you interested in PR that adds ability to use variables in assets properties such as path and label?
16.13.4
to 16.14.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Is there a way to release to a different github repository? What would be required to add that functionality?
Cheers, L~
I had this in the logs:
[Semantic release]: Call plugin verify-conditions
[Semantic release]: Verify authentication for registry https://artifacts.schibsted.io/artifactory/api/npm/npm-local/
[Semantic release]: Wrote NPM_USERNAME, NPM_PASSWORD and NPM_EMAIL to .npmrc.
[Semantic release]: An error occurred while running semantic-release: { [Error: ]
message: ' ',
code: 406,
status: 'Not Acceptable',
headers:
npm plugin write out the URL, but github did not. I figured out my issue (it was because my path prefix was the full path instead of just the path), but if the plugin had printed the url out before attempting the auth, that would have really helped.
(this was using semantic-release --debug
, so I find it odd it did not print anything)
15.13.0
to 15.13.1
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 6 commits.
a44d541
fix: remove obsolete mapTo: input
for .users.addEmails()
7b2c25a
fix: remove obsolete preview headers
afd7fdf
test: replace test using obsolete preview header
89ab485
docs: remove obsolete client.gitdata.getCommitSignatureVerification() and client.gitdata.getTagSignatureVerification()
eb2c908
deprecate: client.gitdata.getCommitSignatureVerification() and client.gitdata.getTagSignatureVerification()
88001fd
test: deprecate client.gitdata.getCommitSignatureVerification() and client.gitdata.getTagSignatureVerification()
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Hey, we updated to v5.2.4 and verifyCondition started to fail as shown in our CircleCI build. We've reverted back to v5.2.1 and everything is working again. From looking at the release notes I can't see that this was intended, any idea what the issue could be?
Branch | Build failing π¨ |
---|---|
Dependency | sinon |
Current Version | 4.1.5 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 10 commits.
68c37ed
Update docs/changelog.md and set new release id in docs/_config.yml
cd8ae51
Add release documentation for v4.1.6
29e80be
4.1.6
a5c59a5
Update History.md and AUTHORS for new release
0ae60b6
Merge pull request #1653 from mroderick/upgrade-dependencies
dcd4191
Upgrade browserify to latest
a316f02
Upgrade markdownlint-cli to latest
78ebdb3
Upgrade lint-staged to latest
fcf967b
Upgrade dependency supports-color
7c3cb4f
Enable StaleBot with default configuration (#1649)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
15.12.0
to 15.12.1
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 10 commits.
2b082ac
fix: push only tags to remote repo
aa022e0
test: clarify variables name
f2ede5b
docs: typo in JS docs
9742712
test: verify errors have message and details
5937f13
test: fix typo
43dbd10
refactor: prefer filter shorter form
9f5645c
refactor: harmonize git utils function names
e594638
test: prefer array spread
244f014
docs: add Codefresh in list of CIs with pipelines
218d830
docs: fix quote marks (#986)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
The semantic-release module is an absolute lifesaver, and I have been using it for the hn module since its first release in august.
Last week, I merged another module (hn-react) into the main repository, making it a monorepo. It uses semantic-release-monorepo to make this work.
When yesterday I made the first release of hn-react from the monorepo, the release was successful. However, it left comments on all merged PRs. These PRs weren't related to the newly released commits, or even the hn-react module.
The release: https://travis-ci.org/headless-ninja/javascript/builds/364652080
Example comment: headless-ninja/javascript#1 (comment)
This doesn't look like expected behaviour.. is there some way to prevent this?
[Semantic release]: Running semantic-release version 15.1.5
[Semantic release]: Running semantic-release version 15.1.5
[Semantic release]: Found git tag hn-react-v1.7.11 associated with version 1.7.11
[Semantic release]: Call plugin analyze-commits
[Semantic release]: Found 7 commits for package hn-react since last release
[Semantic release]: Analysis of 7 commits complete: patch release
[Semantic release]: The next release version is 1.7.12
[Semantic release]: Call plugin verify-release
[Semantic release]: Call plugin generateNotes
[Semantic release]: Found 7 commits for package hn-react since last release
[Semantic release]: Call plugin prepare
[Semantic release]: Wrote version 1.7.12 to package.json
[Semantic release]: Create tag hn-react-v1.7.12
[Semantic release]: Call plugin publish
[Semantic release]: Publishing version 1.7.12 to npm registry
+ [email protected][Semantic release]: Published GitHub release: https://github.com/headless-ninja/javascript/releases/tag/hn-react-v1.7.12
[Semantic release]: Added comment to issue #24: https://github.com/headless-ninja/javascript/pull/24#issuecomment-380132006
[Semantic release]: Added comment to issue #17: https://github.com/headless-ninja/javascript/pull/17#issuecomment-380132016
[Semantic release]: Added comment to issue #16: https://github.com/headless-ninja/javascript/pull/16#issuecomment-380132024
[Semantic release]: Added comment to issue #15: https://github.com/headless-ninja/javascript/pull/15#issuecomment-380132034
[Semantic release]: Added comment to issue #14: https://github.com/headless-ninja/javascript/pull/14#issuecomment-380132042
[Semantic release]: Added comment to issue #13: https://github.com/headless-ninja/javascript/pull/13#issuecomment-380132052
[Semantic release]: Added comment to issue #3: https://github.com/headless-ninja/javascript/pull/3#issuecomment-380132062
[Semantic release]: Added comment to issue #1: https://github.com/headless-ninja/javascript/pull/1#issuecomment-380132068
[Semantic release]: Added comment to issue #23: https://github.com/headless-ninja/javascript/issues/23#issuecomment-380132077
[Semantic release]: Added comment to issue #2: https://github.com/headless-ninja/javascript/pull/2#issuecomment-380132085
[Semantic release]: Published release: 1.7.12
This is more of a question than an issue, since maybe my configuration is wrong. My build creates files that have the same name; something like this:
dist/
lib/
merge.js
merge.min.js
browser/
merge.js
merge.min.js
In my release config, with github.assets
configured as a glob:
assets: ['dist/{lib,umd,browser,module}/*.js']
or
assets: 'dist'
or
assets: ['dist/**/*']
my build in Travis CI would throw this Validation Failed / name exists error. Files were actually getting published to NPM and GitHub, but the GitHub release was flattening the paths, so only one of the merge.js
and merge.min.js
files was actually getting published to github.
When I configure each file individually in github.assets
, like this:
assets: [{
name: 'lib.merge.js'
path: 'dist/lib/merge.js'
} ...]
the error goes away and all files are correctly released in github. I guess my questions are:
It would be much easier to use a glob so I wouldn't have to explicitly set each file's name and path... and that would be the behavior I would expect from a glob. Any help on how to do this is much appreciated.
7.0.0
to 7.0.1
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
fs-extra is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 7 commits.
a32c852
7.0.1
6392917
Temporarily disable standard-markdown
ddc1a2f
Fix removeSync() to eliminate spurious ENOTEMPTY errors on Windows (#646)
ab254b1
Added docs/ and CHANGELOG.md to .npmignore (#642) (#643)
287f234
Fix typo in docs (#628)
402c1d0
Show support for mode (#587)
4da17fe
Chore: github issue template (#617)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Hello,
I'm not sure which version introduced this issue, but I know it happens as far back as 5.2.1 for me (It happened on 5.2.5 and 5.2.6).
I'm seeing the following only when PRs are merged:
[14:14:30] [semantic-release] [@semantic-release/github] βΊ βΉ Added comment to issue #538: https://github.enterprise.com/ORG/plugin-cli/pull/538#issuecomment-518258
[14:14:33] [semantic-release] [@semantic-release/github] βΊ βΉ Added comment to issue #539: https://github.enterprise.com/ORG/plugin-cli/pull/539#issuecomment-518259
[14:14:36] [semantic-release] [@semantic-release/github] βΊ βΉ Added comment to issue #541: https://github.enterprise.com/ORG/plugin-cli/pull/541#issuecomment-518260
[14:15:06] [semantic-release] [@semantic-release/github] βΊ β Failed to add a comment to the issue #538.
[14:15:09] [semantic-release] [@semantic-release/github] βΊ β Failed to add a comment to the issue #539.
[14:15:12] [semantic-release] [@semantic-release/github] βΊ β Failed to add a comment to the issue #541.
semantic-release:github found semantic-release issues: [] +42s
[14:15:12] [semantic-release] βΊ β Failed step "success" of plugin "@semantic-release/github"
[14:15:12] [semantic-release] βΊ β An error occurred while running semantic-release: { HttpError: Invalid request.
For 'links/2/schema', {"labels"=>["released"]} is not an array.
at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
name: 'HttpError',
status: 422,
headers:
{ 'access-control-allow-origin': '*',
'access-control-expose-headers': 'ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval',
connection: 'close',
'content-length': '209',
'content-security-policy': 'default-src \'none\'',
'content-type': 'application/json; charset=utf-8',
date: 'Fri, 14 Dec 2018 14:15:06 GMT',
server: 'GitHub.com',
status: '422 Unprocessable Entity',
'strict-transport-security': 'max-age=31536000; includeSubdomains',
'x-accepted-oauth-scopes': '',
'x-content-type-options': 'nosniff',
'x-frame-options': 'deny',
'x-github-enterprise-version': '2.12.22',
'x-github-media-type': 'github.v3; format=json',
'x-github-request-id': 'b067d086-6b6f-4824-92d1-c0791379a377',
'x-oauth-scopes': 'admin:public_key, public_repo, repo:status',
'x-runtime-rack': '0.023969',
'x-xss-protection': '1; mode=block' },
request:
{ method: 'POST',
url: 'https://github.enterprise.com/api/v3/repos/ORG/plugin-cli/issues/538/labels',
headers:
{ accept: 'application/vnd.github.v3+json',
'user-agent': 'octokit.js/16.2.0 Node.js/8.14.0 (Linux 3.13; x64)',
authorization: 'token [secure]',
'content-type': 'application/json; charset=utf-8' },
body: '{"labels":["released"]}',
request: { validate: [Object] } },
documentation_url: 'https://developer.github.com/enterprise/2.12/v3/issues/labels/#add-labels-to-an-issue',
attemptNumber: 4,
retriesLeft: 0,
pluginName: '@semantic-release/github' }
[14:15:12] [semantic-release] βΊ β An error occurred while running semantic-release: { HttpError: Invalid request.
For 'links/2/schema', {"labels"=>["released"]} is not an array.
at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
name: 'HttpError',
status: 422,
headers:
{ 'access-control-allow-origin': '*',
'access-control-expose-headers': 'ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval',
connection: 'close',
'content-length': '209',
'content-security-policy': 'default-src \'none\'',
'content-type': 'application/json; charset=utf-8',
date: 'Fri, 14 Dec 2018 14:15:09 GMT',
server: 'GitHub.com',
status: '422 Unprocessable Entity',
'strict-transport-security': 'max-age=31536000; includeSubdomains',
'x-accepted-oauth-scopes': '',
'x-content-type-options': 'nosniff',
'x-frame-options': 'deny',
'x-github-enterprise-version': '2.12.22',
'x-github-media-type': 'github.v3; format=json',
'x-github-request-id': 'c63d49e8-b108-43ce-9a88-b616e1fa3281',
'x-oauth-scopes': 'admin:public_key, public_repo, repo:status',
'x-runtime-rack': '0.029809',
'x-xss-protection': '1; mode=block' },
request:
{ method: 'POST',
url: 'https://github.enterprise.com/api/v3/repos/ORG/plugin-cli/issues/539/labels',
headers:
{ accept: 'application/vnd.github.v3+json',
'user-agent': 'octokit.js/16.2.0 Node.js/8.14.0 (Linux 3.13; x64)',
authorization: 'token [secure]',
'content-type': 'application/json; charset=utf-8' },
body: '{"labels":["released"]}',
request: { validate: [Object] } },
documentation_url: 'https://developer.github.com/enterprise/2.12/v3/issues/labels/#add-labels-to-an-issue',
attemptNumber: 4,
retriesLeft: 0,
pluginName: '@semantic-release/github' }
[14:15:12] [semantic-release] βΊ β An error occurred while running semantic-release: { HttpError: Invalid request.
For 'links/2/schema', {"labels"=>["released"]} is not an array.
at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
name: 'HttpError',
status: 422,
headers:
{ 'access-control-allow-origin': '*',
'access-control-expose-headers': 'ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval',
connection: 'close',
'content-length': '209',
'content-security-policy': 'default-src \'none\'',
'content-type': 'application/json; charset=utf-8',
date: 'Fri, 14 Dec 2018 14:15:12 GMT',
server: 'GitHub.com',
status: '422 Unprocessable Entity',
'strict-transport-security': 'max-age=31536000; includeSubdomains',
'x-accepted-oauth-scopes': '',
'x-content-type-options': 'nosniff',
'x-frame-options': 'deny',
'x-github-enterprise-version': '2.12.22',
'x-github-media-type': 'github.v3; format=json',
'x-github-request-id': 'bfcc035e-b3a3-4bbb-8ea7-c5207ade3b3d',
'x-oauth-scopes': 'admin:public_key, public_repo, repo:status',
'x-runtime-rack': '0.024596',
'x-xss-protection': '1; mode=block' },
request:
{ method: 'POST',
url: 'https://github.enterprise.com/api/v3/repos/ORG/plugin-cli/issues/541/labels',
headers:
{ accept: 'application/vnd.github.v3+json',
'user-agent': 'octokit.js/16.2.0 Node.js/8.14.0 (Linux 3.13; x64)',
authorization: 'token [secure]',
'content-type': 'application/json; charset=utf-8' },
body: '{"labels":["released"]}',
request: { validate: [Object] } },
documentation_url: 'https://developer.github.com/enterprise/2.12/v3/issues/labels/#add-labels-to-an-issue',
attemptNumber: 4,
retriesLeft: 0,
pluginName: '@semantic-release/github' }
{ AggregateError:
HttpError: Invalid request.
For 'links/2/schema', {"labels"=>["released"]} is not an array.
at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
at <anonymous>
HttpError: Invalid request.
For 'links/2/schema', {"labels"=>["released"]} is not an array.
at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
at <anonymous>
HttpError: Invalid request.
For 'links/2/schema', {"labels"=>["released"]} is not an array.
at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
at <anonymous>
at /home/circleci/project/node_modules/semantic-release/lib/plugins/pipeline.js:53:11
at <anonymous> name: 'AggregateError' }error Command failed with exit code 1.
at <anonymous> name: 'AggregateError' }error Command failed with exit code 1.
My config looks like:
β node release.config.js
config : {"prepare":["@semantic-release/npm","@semantic-release/git"],"plugins":["@semantic-release/commit-analyzer","@semantic-release/release-notes-generator","@semantic-release/npm",["@semantic-release/github",{"releasedLabels":false}]]}
Any help or direction on how to fix this would be wonderful. I'm not sure when it started, but it is making it hard to release continuously.
I received the following header in the auto-created issue:
π¨ The automated release from the
undefined
branch failed. π¨
It looks like fail.js
isn't yet updated to the changes branches
brought with it.
Line 12 in 9ab2cf2
options.branches
would be the thing to use but that obviously doesn't work anymore for this logic of noting the branch the release failed on since it allows for multiple branches now. Perhaps the current branch/PR branch name needs to be used instead?
I can try to run this again with --debug
if this information isn't enough, so please let me know.
The label name should configurable. Ideally, once semantic-release/semantic-release#563 is implemented, it should contain a channel
variable that will allow to generate a different label for channel on which the fix/feature is included.
For example with the label name released-in-${channel}
we would add released-in-@next
when releasing on @next
and released-in-@latest
once the release is added to @latest
.
Branch | Build failing π¨ |
---|---|
Dependency | debug |
Current Version | 3.2.1 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
debug is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
I'm seeing an unexpected behavior during the publish step. I'm running a Jenkins job against Enterprise github. semantic-release is calculating the correct version based on the commit message and pushes a tag. GH responds with 406, the build fails, but the tag is successfully pushed to the repo.
What I understand 406 "Not Acceptable" to be is response given in place of a more cryptic one.
I can successfully generate and push a tag via the Jenkins job with git commands. Any ideas what the issue might be?
"repository": {
"type": "git",
"url": "git@[enterprise.company.com]:[path]/[repo-name].git"
},
"keywords": ["fix", "feat", "chore"],
"release": {
"analyzeCommits": "@semantic-release/commit-analyzer",
"verifyConditions": "@semantic-release/npm",
"generateNotes": "@semantic-release/release-notes-generator",
"prepare": "@semantic-release/npm",
"publish": "@semantic-release/github",
"success": false,
"fail": false,
"branch": "origin/dev",
"npmPublish": false
}
[14:24:31] [semantic-release] Created tag v0.15.1
[14:24:31] [semantic-release] Start step "publish" of plugin "@semantic-release/github"
[14:24:31] [semantic-release] [@semantic-release/github] Verify GitHub authentication (https://[enterprise.company.com])
[14:24:40] [semantic-release] ΓΒ» Γβ Failed step "publish" of plugin "@semantic-release/github"
[14:24:40] [semantic-release] An error occurred while running semantic-release: { HttpError
at response.text.then.message (C:\Jenkins\jobs\semver-pipeline\workspace\node_modules\@octokit\request\lib\request.js:55:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
name: 'HttpError',
status: 406,
headers:
{ 'cache-control': 'no-cache, no-store',
connection: 'close',
'content-security-policy': 'default-src \'none\'; base-uri \'self\'; block-all-mixed-content; connect-src \'self\' [enterprise.company.com] status.github.com wss://[enterprise.company.com]; font-src
\'self\'; form-action \'self\' [enterprise.company.com]; frame-ancestors \'none\'; frame-src \'self\'; img-src * data:; manifest-src \'self\'; media-src \'none\'; script-src \'self\'; style-src
\'unsafe-inline\' \'self\'',
'content-type': 'text/html; charset=utf-8',
date: 'Mon, 11 Feb 2019 19:24:41 GMT',
'referrer-policy': 'origin-when-cross-origin, strict-origin-when-cross-origin',
server: 'GitHub.com',
'set-cookie': 'has_recent_activity=1; path=/; expires=Mon, 11 Feb 2019 20:24:41 -0000, _fi_sess=MDEyOEZ5NXFTQ0tkK1dsZmMybk5Sa2FuL0RldldCY2RDbXZ3aVJYR0h3VzhmUDJxeUNDUVJTblFpNWRwcWNuMGtycXB
FcjV3Q1NVM1NwOFJTWldIRExnVTNTM2hNVG8xRDhUL1AyaitXUWZPNTdEeTJicEMyNE5vaXhUaFhtaklBQXFKNHE0RWN4OVdwbU01VEVJQzh3VjY1MGZDN01ubGpwMmlsbGJhNVM5QlRUK2pUaXNiamNtdCt5UzNTdVcyMmczOEFERE9XNCtHRmo5TzdSOWd
xeGVrTEVUOE5pcGpkTzZBcXhIc3FkQjlrbVE4OGVGeFhyaUpuQlYrMnFnK0hEVHk3dXI0YUx5eFVta0p5OXJNa3VuREhneXZsUUEzQlZiaVdjczNVNjQ4S1puQlMxSVAwalhQUzlMMDVPUkQtLXluNE1wQmh5eG9nY0hQbEVuQkQrcnc9PQ%3D%3D--c1b2e
f457aca21057a2f756d139bdf1db40dfd3d; path=/; secure; HttpOnly',
status: '406 Not Acceptable',
'strict-transport-security': 'max-age=31536000; includeSubdomains',
'transfer-encoding': 'chunked',
vary: 'X-PJAX',
'x-content-type-options': 'nosniff',
'x-frame-options': 'deny',
'x-github-request-id': '6c023ef4-b4e1-4891-9ff2-7e0d4522e23d',
'x-request-id': '1f966a6e-d362-4d1d-a253-80c5882a5a5d',
'x-runtime': '0.008736',
'x-runtime-rack': '0.013532',
'x-xss-protection': '1; mode=block' },
request:
{ method: 'GET',
url: 'https://[enterprise.company.com]/repos/[path]/[repo-name]',
headers:
{ accept: 'application/vnd.github.v3+json',
'user-agent': 'octokit.js/16.13.3 Node.js/8.11.3 (Windows Server 2012; x64)',
authorization: 'token [secure]' },
request: { agent: undefined, validate: [Object] } },
attemptNumber: 4,
retriesLeft: 0,
pluginName: '@semantic-release/github' }
Branch | Build failing π¨ |
---|---|
Dependency | semantic-release |
Current Version | 15.8.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 1 commits.
3fb3fa8
fix: do not override env variable with default if defined
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
We are using @semantic-release/github
and we would like to know the recommended configuration to work with protection:
Our release branch is master
,
So far we did try to protect using:
body='{
"required_status_checks": {
"strict":true,
"contexts": [
"continuous-integration/travis-ci"
]
},
"enforce_admins": true,
"required_pull_request_reviews": null,
"restrictions": {
"users": [
"kopax"
],
"teams": [
"developers"
]
}
}'
curl -sS -L -X PUT \
-H "Authorization: token ${GH_TOKEN:-$GITHUB_TOKEN}" \
-H "Accept: application/vnd.github.luke-cage-preview+json" \
"https://api.github.com/repos/${scope}/${name}/branches/dev/protection" \
--compressed \
--data-binary "$body"
curl -sS -L -X PUT \
-H "Authorization: token ${GH_TOKEN:-$GITHUB_TOKEN}" \
-H "Accept: application/vnd.github.luke-cage-preview+json" \
"https://api.github.com/repos/${scope}/${name}/branches/master/protection" \
--compressed \
--data-binary "$body"
We get the following error:
{ Error: Command failed: git push --tags https://[secure]@github.com/yeutech-lab/accept-dot-path.git HEAD:master
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: Required status check "continuous-integration/travis-ci" is expected.
To https://github.com/yeutech-lab/accept-dot-path.git
! [remote rejected] HEAD -> master (protected branch hook declined)
I assume we should disable travis ci check, but that seems a bit odd decision, how do you users of semantic-release
recommand to configure the protection on GitHub?
https://github.com/cheton/github-release-cli and the Travis GitHub deploy provider support this.
One use case is it's nice to suffix the binary with the version string.
βοΈ Greenkeeperβs updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing π¨ |
---|---|
Dependency | @octokit/rest |
Current Version | 15.1.7 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 4 commits.
bf2f550
fix: remove obsolete github.search.email() API (#795)
505ed1f
chore(package): update semantic-release to version 15.0.0
60bdd7a
docs(README): remove @next
npm badge
44d6161
build(package): publish to @latest
by default
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
I've only been using semantic-release for a few days, so I may not fully understand how it works, so this may just be my misunderstanding.
Here's a recent issue that was meant to use the below config: Colonise/DataSource#29
I've configured my package.json
like so:
"publish": [
{
"path": "@semantic-release/github",
"successComment": "This ${issue.pull_request ? 'pull request has been included in' : 'issue has been resolved in'} **[release ${nextRelease.gitTag}](https://github.com/Colonise/DataSource/releases/tag/${nextRelease.gitTag})**!\\n\\nYou can install the **[npm package](https://www.npmjs.com/package/@colonise/datasource)** for ${nextRelease.gitTag} using `npm install @colonise/datasource@${nextRelease.version}`\\n\\n_Automatically generated by [semantic-release](https://github.com/semantic-release/semantic-release)._",
"failTitle": "The automatic publishing of release ${nextRelease.gitTag} is failing"
},
"@semantic-release/npm"
]
Cheers
when working with feature branches, only the branch/PR itself gets a comment - it would be awesome if all PRs merged previously into feature branch also could get a comment. π
16.12.0
to 16.13.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 10 commits.
0ae98ae
refactor: github.
-> octokit.
722fb21
docs(README): github. -> octokit.
6ee188a
docs(HOW_IT_WORKS): replace .authenticate()
method with auth
construction option
3b81bea
test: replace deprecated octokit.authenticate method with "auth" constructor option
162ab2b
test: deprecated octokit.authenticate()
45a4836
feat: "auth" constructor options
1da3515
refactor: default constructor options to {} before passing to plugins
5c6bade
test: "auth" constructor option
8b2ba2b
docs(README): Replace depreceated octokit.authenticate
with auth
constructor option
d7bced7
docs(README): update "API Previews"
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
In v15.2.0 we deprecated
options.headers
options.port
options.pathPrefix
options.host
in favour of options.baseUrl
. That logs quite a lot of deprecation warnings in semantic-release now. Iβll fix that
Hi,
Seeing an error about semantic-release not able to push to github, even though the build has a GITHUB_TOKEN env var.
[semantic-release] βΊ β The command "git push --dry-run https://[secure]@www.github.com/lirantal/opn-shell.git HEAD:master" failed with the error message remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/lirantal/opn-shell.git/'
Travis build: https://travis-ci.org/lirantal/opn-shell/jobs/483803564
What should I be looking into?
π
We're using semantic-release/github
plugin to publish assets to each release we make with semantic-release
.
The release configuration is as follows:
{
"prepare": [
"@semantic-release/npm",
{
"path": "@semantic-release/exec",
"cmd": "npm i -g pkg && pkg ."
}
],
"publish": [
"@semantic-release/npm",
{
"path": "@semantic-release/github",
"assets": [
{
"path": "./snyk-linux",
"name": "snyk-linux",
"label": "snyk-linux"
},
{
"path": "./snyk-macos",
"name": "snyk-macos",
"label": "snyk-macos"
},
{
"path": "./snyk-win.exe",
"name": "snyk-win.exe",
"label": "snyk-win.exe"
}
]
}
]
}
The assets are being published as expected, however the plugin fails over a 422 response from GH:
[06:49:06] [semantic-release] βΊ β An error occurred while running semantic-release: { HttpError: {"message":"Validation Failed","request_id":"AA68:095A:1D9FF3:201218:5B7D0761","documentation_url":"https://developer.github.com/v3","errors":[{"resource":"ReleaseAsset","code":"already_exists","field":"name"}]}
at response.text.then.message (/home/travis/.nvm/versions/node/v8.11.4/lib/node_modules/semantic-release/node_modules/@octokit/rest/lib/request/request.js:72:19)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
name: 'HttpError',
code: 422,
status: undefined,
headers:
{ 'cache-control': 'no-cache',
connection: 'close',
'content-length': '211',
'content-security-policy': 'default-src \'none\'',
'content-type': 'application/json; charset=utf-8',
date: 'Wed, 22 Aug 2018 06:49:06 GMT',
'strict-transport-security': 'max-age=31557600',
'x-accepted-oauth-scopes': 'repo',
'x-content-type-options': 'nosniff',
'x-frame-options': 'deny',
'x-github-media-type': 'github.v3; format=json',
'x-github-request-id': 'AA68:095A:1D9FF3:201218:5B7D0761',
'x-oauth-scopes': 'repo',
'x-xss-protection': '1; mode=block' },
pluginName: '@semantic-release/github' }
{ HttpError: {"message":"Validation Failed","request_id":"AA68:095A:1D9FF3:201218:5B7D0761","documentation_url":"https://developer.github.com/v3","errors":[{"resource":"ReleaseAsset","code":"already_exists","field":"name"}]}
at response.text.then.message (/home/travis/.nvm/versions/node/v8.11.4/lib/node_modules/semantic-release/node_modules/@octokit/rest/lib/request/request.js:72:19)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
name: 'HttpError',
code: 422,
status: undefined,
headers:
{ 'cache-control': 'no-cache',
connection: 'close',
'content-length': '211',
'content-security-policy': 'default-src \'none\'',
'content-type': 'application/json; charset=utf-8',
date: 'Wed, 22 Aug 2018 06:49:06 GMT',
'strict-transport-security': 'max-age=31557600',
'x-accepted-oauth-scopes': 'repo',
'x-content-type-options': 'nosniff',
'x-frame-options': 'deny',
'x-github-media-type': 'github.v3; format=json',
'x-github-request-id': 'AA68:095A:1D9FF3:201218:5B7D0761',
'x-oauth-scopes': 'repo',
'x-xss-protection': '1; mode=block' },
pluginName: '@semantic-release/github' }
More details at https://travis-ci.org/snyk/snyk/jobs/419030290
I appreciate the fact this may be on GH side, opened a support ticket with them, will update here once I hear back.
Wanted to document the issue here, maybe there's more context?
Branch | Build failing π¨ |
---|---|
Dependency | github |
Current Version | 12.0.4 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
github is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
filePath
as query parameter (3c2e465)There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
See https://travis-ci.org/semantic-release/github/jobs/345779998#L506
We should probably exclude issues from other repo anyway, as we don't want to be invasive and add comments to someone else repo.
I'm using semantic-release
in a Drone CI + GitHub Enterprise setup. I have one project working successfully and have started updating our remaining JS projects to use semantic-release
as well. I have run into a failure that I can't easily see what is happening:
This is the output:
[Semantic release]: Running semantic-release version 15.7.0
[Semantic release]: Load plugin "verifyConditions" from @semantic-release/npm
[Semantic release]: Load plugin "verifyConditions" from @semantic-release/github
[Semantic release]: Load plugin "analyzeCommits" from @semantic-release/commit-analyzer
[Semantic release]: Load plugin "generateNotes" from @semantic-release/release-notes-generator
[Semantic release]: Load plugin "prepare" from @semantic-release/npm
[Semantic release]: Load plugin "publish" from @semantic-release/npm
[Semantic release]: Load plugin "publish" from @semantic-release/github
[Semantic release]: Load plugin "success" from @semantic-release/github
[Semantic release]: Load plugin "fail" from @semantic-release/github
[Semantic release]: Run automated release from branch master
[Semantic release]: Call plugin "verifyConditions"
[Semantic release]: Verify authentication for registry https://registry.npmjs.itcs.hpecorp.net
[Semantic release]: Wrote NPM_TOKEN to .npmrc.
[Semantic release]: Call plugin "verifyConditions"
[Semantic release]: Verify GitHub authentication (https://github.hpe.com/api/v3)
[Semantic release]: Found git tag v1.0.1 associated with version 1.0.1
[Semantic release]: Found 1 commits since last release
[Semantic release]: Call plugin "analyzeCommits"
[Semantic release]: Analyzing commit: fix: replace broken link to wiki
[Semantic release]: The release type for the commit is patch
[Semantic release]: Analysis of 1 commits complete: patch release
[Semantic release]: The next release version is 1.0.2
[Semantic release]: Call plugin "generateNotes"
[Semantic release]: Call plugin "prepare"
[Semantic release]: Wrote version 1.0.2 to package.json
[Semantic release]: Wrote version 1.0.2 to package-lock.json
[Semantic release]: Create tag v1.0.2
[Semantic release]: Call plugin "publish"
[Semantic release]: Publishing version 1.0.2 to npm registry
+ @hpe/[email protected][Semantic release]: Call plugin "publish"
[Semantic release]: Published GitHub release: https://github.hpe.com/zookeeper/zookeeper/releases/tag/v1.0.2
[Semantic release]: Call plugin "success"
[Semantic release]: An error occurred while running semantic-release: { HttpError: {"message":"Validation Failed","errors":[{"message":"The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them.","resource":"Search","field":"q","code":"invalid"}],"documentation_url":"https://developer.github.com/enterprise/2.13/v3/search/"}
at response.text.then.message (/drone/src/github.hpe.com/zookeeper/zookeeper/node_modules/@octokit/rest/lib/request/request.js:78:19)
at process._tickCallback (internal/process/next_tick.js:68:7)
name: 'HttpError',
code: 422,
status: undefined,
headers:
{ 'access-control-allow-origin': '*',
'access-control-expose-headers':
'ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval',
'cache-control': 'no-cache',
connection: 'close',
'content-length': '322',
'content-security-policy': 'default-src \'none\'',
'content-type': 'application/json; charset=utf-8',
date: 'Tue, 10 Jul 2018 21:25:03 GMT',
server: 'GitHub.com',
status: '422 Unprocessable Entity',
'strict-transport-security': 'max-age=31536000; includeSubdomains',
'x-accepted-oauth-scopes': '',
'x-content-type-options': 'nosniff',
'x-frame-options': 'deny',
'x-github-enterprise-version': '2.13.5',
'x-github-media-type': 'github.v3; format=json',
'x-github-request-id': 'b811cf9b-3264-43f4-b396-b1b0d84dde6f',
'x-oauth-scopes': 'repo',
'x-runtime-rack': '0.058855',
'x-xss-protection': '1; mode=block' },
pluginName: '@semantic-release/github' }
{ AggregateError:
HttpError: {"message":"Validation Failed","errors":[{"message":"The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them.","resource":"Search","field":"q","code":"invalid"}],"documentation_url":"https://developer.github.com/enterprise/2.13/v3/search/"}
at response.text.then.message (/drone/src/github.hpe.com/zookeeper/zookeeper/node_modules/@octokit/rest/lib/request/request.js:78:19)
at /drone/src/github.hpe.com/zookeeper/zookeeper/node_modules/semantic-release/lib/plugins/pipeline.js:53:11 name: 'AggregateError' }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @hpe/[email protected] semantic-release: `semantic-release`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @hpe/[email protected] semantic-release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-07-10T21_25_03_520Z-debug.log
This is my .drone.yml
pipeline step where I run semantic-release
:
semantic-release:
image: node
commands:
- npm run semantic-release
secrets: [ npm_token, github_token ]
This is my .releaserc
:
{
"branch": "master",
"githubUrl": "https://github.hpe.com",
"githubApiPathPrefix": "/api/v3"
}
It is getting all the way through publishing to our internal npm registry as well as creating the release in GitHub. The failure seems to be occurring where it is doing some kind of search related to updating issues or PRs?
Is there any additional debugging I can turn on? Is this something that is possibly documented already that I haven't found?
Thank you in advance
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.