-
Notifications
You must be signed in to change notification settings - Fork 1
Fix maven release #50
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
Conversation
…lugin:0.7.0") to build.gradle.kts
…ion to make it three parts as necessary
…from the version string as JReleaser expects that
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.
Pull Request Overview
The workflow replaces the existing Sonatype publishing steps with a JReleaser-based sequence and adds the necessary environment variables for GPG and Maven Central integration.
- Switch from direct
publishToSonatype
tasks tojreleaserConfig
,publish
, andjreleaserFullRelease
commands with increased JVM heap. - Introduce JReleaser-specific secrets for GPG keys, GitHub token, and Maven Central credentials.
Comments suppressed due to low confidence (1)
.github/workflows/run-publish-maven.yml:53
- [nitpick] The secret
BIOKOTLINMAVEN
name is ambiguous for a GitHub token. Consider using or renaming to the standardGITHUB_TOKEN
or a clearer secret name to indicate its purpose.
JRELEASER_GITHUB_TOKEN: ${{ secrets.BIOKOTLINMAVEN }}
@@ -41,9 +41,16 @@ jobs: | |||
run: chmod +x ./gradlew | |||
|
|||
- name: Publish to Maven Central Repository | |||
run: conda run ./gradlew clean publishToSonatype closeAndReleaseSonatypeStagingRepository --no-daemon | |||
run: conda run --no-capture-output bash -c "./gradlew jreleaserConfig && ./gradlew clean && ./gradlew publish && ./gradlew jreleaserFullRelease -Dorg.gradle.jvmargs=\"-Xmx8g\"" |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
No description provided.