Repository navigation
ci: add Maven Central release pipeline for tagged versions - #38
Merged
Merged
Conversation
Signed-off-by: Zhoujie628 <zhoujie628@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #37
Summary
v*tags): secrets validation, GPG key import, scoped verify, then deployworkflow-engineandspring-boot-starterto Maven Central via the Central Portal.v0.1.0->0.1.0); the pom keeps its internal development revision.autoPublish=true+waitUntil=validated(the previous combination deadlocks unattended runs).samplesstays out of deployment (maven.deploy.skip; vendor jar unavailable on Central).CI impact
None for existing pipelines: the workflow triggers only on
v*tags, and the pom change only affects thedeploygoal, which CI does not execute. Verified locally with the exact CI command (mvn clean verify -pl workflow-engine,spring-boot-starter -am): green.Follow-up
First release additionally requires the
dev.openannamespace claim on the Central Portal (openan.dev DNS TXT record), tracked separately.