The automated release is failing 🚨

[evansiroky]

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Deployment to maven failed.

The deployment to maven failed for an unknown reason.

Please check the logs on the CI server to see what happened.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[landonreed]

Sonatype is undergoing scheduled maintenance: https://twitter.com/sonatype_ops/status/1334575184854962176

We should check the status/restart the build in an hour or so.

EDIT: I restarted the build, but it looks like the 6.2.0 tag did not get detected/uploaded to sonatype. @evansiroky, do you have any insights here? https://travis-ci.com/github/conveyal/gtfs-lib/builds/206388643

[evansiroky]

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Deployment to maven failed.

The deployment to maven failed for an unknown reason.

Please check the logs on the CI server to see what happened.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[landonreed]

Latest failure logs (line 17335):

Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/comconveyal-1111/com/conveyal/gtfs-lib/6.2.1/gtfs-lib-6.2.1.pom.asc (819 B at 11 kB/s)
Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/comconveyal-1111/com/conveyal/gtfs-lib/6.2.1/gtfs-lib-6.2.1-shaded.jar
Progres[8:06:12 PM] [semantic-release] [@semantic-release/github] › ���  Found existing semantic-release issue #300.
Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/comconveyal-1111/com/conveyal/gtfs-lib/6.2.1/gtfs-lib-6.2.1-shaded.jar (16 MB at 13 MB/s)
[INFO]  * Upload of locally staged artifacts finished.
[INFO]  * Closing staging repository with ID "comconveyal-1111".
Waiting for operation to complete...
....
[ERROR] Remote staging finished with a failure: A message body reader for Java class com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO, and Java type class com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO, and MIME media type text/html was not found
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:14 min
[INFO] Finished at: 2020-12-09T20:06:12Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy (injected-nexus-deploy) on project gtfs-lib: Remote staging failed: A message body reader for Java class com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO, and Java type class com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO, and MIME media type text/html was not found -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
    at makeError (/home/travis/.config/yarn/global/node_modules/@conveyal/maven-semantic-release/node_modules/execa/index.js:172:9)
    at /home/travis/.config/yarn/global/node_modules/@conveyal/maven-semantic-release/node_modules/execa/index.js:277:16
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async deploy (/home/travis/.config/yarn/global/node_modules/@conveyal/maven-semantic-release/lib/maven.js:47:5)
    at async publish (/home/travis/.config/yarn/global/node_modules/@conveyal/maven-semantic-release/lib/publish.js:16:5)
    at async validator (/home/travis/.config/yarn/global/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
    at async /home/travis/.config/yarn/global/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
    at async /home/travis/.config/yarn/global/node_modules/semantic-release/lib/plugins/pipeline.js:31:3
    at async Object.pluginsConf.<computed> [as publish] (/home/travis/.config/yarn/global/node_modules/semantic-release/lib/plugins/index.js:80:11)
[8:06:12 PM] [semantic-release] › ✖  Failed step "publish" of plugin "@conveyal/maven-semantic-release"
[@octokit/rest] `const Octokit = require("@octokit/rest")` is deprecated. Use `const { Octokit } = require("@octokit/rest")` instead
[8:06:13 PM] [semantic-release] [@semantic-release/github] › ℹ  Added comment to issue #300: https://github.com/conveyal/gtfs-lib/issues/300#issuecomment-742017374.
[8:06:13 PM] [semantic-release] › ✔  Completed step "fail" of plugin "@semantic-release/github"
[8:06:13 PM] [semantic-release] › ✖  EMAVENDEPLOY Deployment to maven failed.
The deployment to maven failed for an unknown reason.
Please check the logs on the CI server to see what happened.
SemanticReleaseError: Deployment to maven failed.
    at getError (/home/travis/.config/yarn/global/node_modules/@conveyal/maven-semantic-release/lib/util.js:24:10)
    at deploy (/home/travis/.config/yarn/global/node_modules/@conveyal/maven-semantic-release/lib/maven.js:54:11)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  code: 'EMAVENDEPLOY',
  details: 'The deployment to maven failed for an unknown reason.\n' +
    '\n' +
    'Please check the logs on the CI server to see what happened.',
  semanticRelease: true,
  pluginName: '@conveyal/maven-semantic-release'
}