search

jcasbin / redis-watcher

Redis watcher for jCasbin
https://github.com/casbin/jcasbin
Apache License 2.0
4 stars 11 forks source link

The automated release is failing 🚨 #18

Closed github-actions[bot] closed 2 years ago

github-actions[bot] commented 2 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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

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 fix 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 are some links that can help you:

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 :package::rocket:

casbin-bot commented 2 years ago

@tangyang9464 @shy1st @fangzhengjin

hsluoyz commented 2 years ago

@seriouszyx plz fix it: https://github.com/jcasbin/redis-watcher/runs/3965469897?check_suite_focus=true

image

seriouszyx commented 2 years ago

@hsluoyz Perhaps the OSSRH secrets in the organization can't be used in this repo. I noticed that permissions granted to @tangyang9464. Can you set your OSSRH secrets for this repo?

tangyang9464 commented 2 years ago

@hsluoyz Perhaps the OSSRH secrets in the organization can't be used in this repo. I noticed that permissions granted to @tangyang9464. Can you set your OSSRH secrets for this repo?

@seriouszyx I set two secrets. You can try again. image

github-actions[bot] commented 2 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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

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 fix 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 are some links that can help you:

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 :package::rocket:

hsluoyz commented 2 years ago

@seriouszyx can you fix this issue?

seriouszyx commented 2 years ago

Sorry, let me test on my own repository for a while.

github-actions[bot] commented 2 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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

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 fix 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 are some links that can help you:

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 :package::rocket:

hsluoyz commented 2 years ago

@seriouszyx @tangyang9464 still failing

seriouszyx commented 2 years ago

@hsluoyz I rechecked our application. Although it's a new project, the groupId is previously configured. So the url we upload should still be https://oss.sonatype.org/ :clown_face:

hsluoyz commented 2 years ago

@seriouszyx PR reverted. Plz find other ways to fix.

hsluoyz commented 2 years ago

@seriouszyx does Maven releasing work?

seriouszyx commented 2 years ago

@hsluoyz available on Staging Repository, it will be synced to the Central Repository after a while.

hsluoyz commented 2 years ago

@seriouszyx sounds good!