-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no configured signatory issue #2
Comments
did you find a solution ? |
@lucasbordini this happens when the signing plugin cannot find credentials. See https://docs.gradle.org/current/userguide/signing_plugin.html#sec:signatory_credentials for more details |
It would kinda be good if that didn't hook automatically on build or can be disable or so, because I just forked a repository in order to work on it (with no intention to publish it myself), but I can build it without setting up signing. Singing sounds to me like something that should happen during the publishing stage and not on any dev build. |
Version 0.0.9 is rolling out with a fix for this. Should be live in a few minutes. |
Thanks |
I have two plugins files under module - convention-plugins which comming from - https://github.com/Kotlin/multiplatform-library-template/tree/main/convention-plugins
was trying to migrate to your plugin but i got some errors.
module.publication.gradle.kts
and root.publication.gradle.kts
but when run gradle publish i got an error below:
The text was updated successfully, but these errors were encountered: