Skip to content

Add automated Maven Central publishing to release workflow - #100

Draft
jeremyprime wants to merge 4 commits into
valkey-io:mainfrom
jeremyprime:feat/maven-publish-workflow
Draft

Add automated Maven Central publishing to release workflow#100
jeremyprime wants to merge 4 commits into
valkey-io:mainfrom
jeremyprime:feat/maven-publish-workflow

Conversation

@jeremyprime

Copy link
Copy Markdown
Collaborator

Summary

Adds a publish job to the release workflow that signs and deploys artifacts to Maven Central (staging) after the existing build/test/release steps complete.

Closes #85

Changes

  • New publish job gated by maven-publish environment approval
  • Uses OIDC to assume AWS IAM role (no static credentials in GitHub)
  • Fetches Maven and GPG credentials from AWS Secrets Manager
  • Configures GPG for non-interactive signing
  • Deploys spring-data-valkey and spring-boot-starter-data-valkey to Sonatype staging

Prerequisites

  • AWS IAM role with OIDC trust policy
  • Secrets in AWS Secrets Manager for Maven credentials and GPG key/passphrase
  • GitHub environment with required reviewers and AWS_ROLE_ARN variable

Signed-off-by: Jeremy Parr-Pearson <jeremy.parr-pearson@improving.com>
Signed-off-by: Jeremy Parr-Pearson <jeremy.parr-pearson@improving.com>
Signed-off-by: Jeremy Parr-Pearson <jeremy.parr-pearson@improving.com>
@jeremyprime
jeremyprime force-pushed the feat/maven-publish-workflow branch from d0b9c69 to 97c7e18 Compare July 29, 2026 22:00
Signed-off-by: Jeremy Parr-Pearson <jeremy.parr-pearson@improving.com>
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 Maven Central publishing in release workflow

1 participant