Skip to content
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

Add CI pipeline to release to Maven Central (#111) #129

Merged
merged 4 commits into from
Apr 10, 2024

Conversation

abelsromero
Copy link
Member

@abelsromero abelsromero commented Apr 9, 2024

Configuration is a port of asciidoctor-maven-plugin configuration

  • Define release profile with required configurations
  • Unify Maven plugin versions under pluginManagement
  • Add Maven Wrapper to be used during release: that reduces variability

Also, add Dependabot to handle GH actions

Closes #111

@abelsromero
Copy link
Member Author

Secrets have already been configured. The Key is the same as asciidoctor-maven-plugin (valid unit 2027-01-20, signed by "Abel Salgado Romero (asciidoctor CI) <my_personal_email>"...because they required a contact email), and the sonatype credentials are a token generated from session.

Configuration is a port of asciidoctor-maven-plugin configuration
Also, add dependabot to handle GH actions

Closes asciidoctor#111
@abelsromero abelsromero changed the title Add CI pipeline to release to Maven Central Add CI pipeline to release to Maven Central (#111) Apr 9, 2024
@abelsromero abelsromero force-pushed the issue-111-automate-releases branch 2 times, most recently from f4a7127 to 92a0b07 Compare April 10, 2024 21:38
@abelsromero abelsromero force-pushed the issue-111-automate-releases branch 2 times, most recently from 9a0099d to 58b56d6 Compare April 10, 2024 22:08
@abelsromero
Copy link
Member Author

Run a local test and all is fine (except I need to use git ssh auth, we need to trust HTTP will work in CI, at least it worked for maven-plugin and release v3.0.0 🤞 )

Artifacts made it into Maven Central "staging", included the shaded jar, in case we go with it.

image

@abelsromero abelsromero marked this pull request as ready for review April 10, 2024 22:15
@abelsromero abelsromero merged commit 65fbeab into asciidoctor:main Apr 10, 2024
3 checks passed
@abelsromero abelsromero deleted the issue-111-automate-releases branch April 11, 2024 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Automate relases using GitHub actions
1 participant