Travis failed to publish release for Chrome
See original GitHub issuehttps://travis-ci.org/sindresorhus/refined-github/builds/637034089#L4475 Response code 400 (Bad Request)
{
"error": {
"errors": [
{
"domain": "global",
"reason": "badRequest",
"message": "Publish condition not met: The single purpose description is required.; A justification for activeTab is required.; A justification for the broad host permission is required.; A justification for remote script is required."
}
],
"code": 400,
"message": "Publish condition not met: The single purpose description is required.; A justification for activeTab is required.; A justification for the broad host permission is required.; A justification for remote script is required."
}
}
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Travis failed to publish release for Chrome #2707 - GitHub
Yep. We have no idea of what that error means, it doesn't exist online, nobody ever mentioned it. All reactions.
Read more >travis-ci/travis-ci - Gitter
The command "sudo -E apt-get -yq --no-install-suggests --no-install-recommends $(travis_apt_get_options) install google-chrome-stable fluxbox" failed and ...
Read more >Google Chrome - Travis CI Docs
For security reasons, Google Chrome is unable to provide sandboxing when it is running in the container-based environment.
Read more >Why does Travis CI report a build success even though the ...
However, the build reported as passing even though the npm publish failed due to the version already existing. Here's the tail end of...
Read more >Travis CI - Intuit
This code will ensure that your git HEAD is on baseBranch when creating a new release. Canary Deploy Failing on Forks. By default...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have manually submitted an update. I didn’t get any new fields to fill in. I only got this after publishing:
It looks like a manual upload fixes the issue (but you still have to wait until it’s published)