[ci] New "Publish Release" workflow #5745
Conversation
|
Compared to main: (comment created at 2025-06-26 13:21:46+00:00 for 6462b0c) |
- add SNAPSHOT links - add latest links
- github-release - create-sourceforge-blog-post - create-regression-tester-baseline - create-docker
That way, a new SNAPSHOT is available sooner and PR don't fail (because of missing regression tester baseline)
ab68cc0 to
85eda52
Compare
for now, we ignore pmd#4446 and release everything in one go.
|
I decided to postpone the task "Figure out a solution when pmd-designer needs to be released at the same time": After the switch from 6.x to 7.x, we didn't need this "feature" yet. Just releasing everything at once when releasing PMD is much simpler, as we don't need to maintain two different release cases (a) release pmd-designer in the middle, and b) no pmd-designer release). That means: if the situation arises, that we would need a new pmd-designer version, but the new pmd-designer version would need a new pmd version, then we might try to create a manual (deploy to maven central only) pre-release of only pmd-core, allowing to release pmd-designer before the "real" release of pmd is happening. |
| -Dmaven.javadoc.skip=false \ | ||
| -Dmaven.source.skip=false |
There was a problem hiding this comment.
This is actually a fix that maybe should be extracted out of this PR, as it affects the snapshot builds.
Currently, no sources and javadoc artifacts are available at https://central.sonatype.com/service/rest/repository/browse/maven-snapshots/net/sourceforge/pmd/pmd-core/
- use correct cache key for regression tester - cleanup gpg key - create correct docs.pmd-code.org/latest symlink
Describe the PR
<deploymentName>${project.artifactId}</deploymentName>for central-publishing-maven-pluginPostponed
Related issues
Ready?
./mvnw clean verifypasses (checked automatically by github actions)