The automated release is failing 🚨

[nodece]

🚨 The automated release from the beta branch failed. 🚨

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 beta 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:

• 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.

---

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch beta on the remote Git repository with URL https://x-access-token:[secure]@github.com/casbin/casbin-core.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[casbin-bot]

@tangyang9464 @closetool @sagilio

[nodece]

🚨 The automated release from the beta branch failed. 🚨

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 beta 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:

• 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.

---

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch beta on the remote Git repository with URL https://x-access-token:[secure]@github.com/casbin/casbin-core.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[Shivansh-yadav13]

Last push cloud be failing due to presence of yarn.lock file, something to do with chalk, in this issue others have suggested some workarounds ,

"resolutions": {
    "npm/chalk": "^4.1.2"
},

@nodece what are your thoughts?

[nodece]

Last push cloud be failing due to presence of yarn.lock file, something to do with chalk, in this issue others have suggested some workarounds ,

"resolutions": {
    "npm/chalk": "^4.1.2"
},

@nodece what are your thoughts?

I'm not sure what happened, this is my personal token.

fatal: unable to access 'https://github.com/casbin/casbin-core.git/': The requested URL returned error: 403.

[nodece]

Disable the semantic-release.