-
Notifications
You must be signed in to change notification settings - Fork 448
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
Attemp to publish beta.1 #3420
Attemp to publish beta.1 #3420
Conversation
Kover Report
|
I'm interested! But I have a few questions, let's start there. Also, KotlinConf is next week, I don't think I'll be able to do much in the coming weeks, do you need anything soon? |
@CLOVIS-AI, no expectations at all |
.github/workflows/publish.yml
Outdated
- name: Publish next major SNAPSHOT version | ||
run: ./gradlew -Pversion=${{ inputs.version }} publish | ||
- name: Publish artifacts | ||
run: ./gradlew -Pversion=2.0.0-alpha.3 publish -Penable_wasm=true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think adding --no-configuration-cache
fixes it (https://vanniktech.github.io/gradle-maven-publish-plugin/central/#automatic-release)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm also struggling with setting up Sonatype publishing for a KMP library and your PR made my day 😄 Almost done with this Gradle + Maven crap
We updated to using Gradle Maven Publish Plugin, but the
publish
command was not doing anything even though the build was green. Nothing showed up in Sonatype, nor in Maven Central.This update uses the older command, I am also using in other projects. It should send to sonatype, but not to Maven Central (yet). If we can get this PR to publish the artefacts, we can merge the changes to main.
CC\ @CLOVIS-AI. Calling you in, since you volunteered to work on our Gradle mess 😅 I think this is the right time to do this, and I think we've already come to an agreement on how on Slack. So if you have time, and are still interested in doing this feel free to open a issue to discuss, a PR with proposal, or whatever you think makes sense 😉