Repository navigation
Update metricshub/workflows to v7 - #139
Conversation
- .github/workflows: maven-build, maven-central-deploy and maven-central-release move from @v4 to @v7. GitHub runners now ship Maven 3.10, and Central snapshot deploys need workflows v7, which declares the central.sonatype.com origin. oss-parent is already 5 and the site already runs on Doxia 2 (maven-site-plugin 4.0.0-M16 with maven-skin-tools 1.8.01, SITE 2.0.0 descriptor), so neither is changed here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4e69ef9313
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| jobs: | ||
| release: | ||
| uses: metricshub/workflows/.github/workflows/maven-central-release.yml@v4 | ||
| uses: metricshub/workflows/.github/workflows/maven-central-release.yml@v7 |
There was a problem hiding this comment.
Update the release instructions for Central Portal
With the v7 release workflow, releases use Central Publishing with server ID central, but README.md:55-62 still directs maintainers to the legacy s01.oss.sonatype.org repository, server ID ossrh, and Nexus staging console. Because autoRelease remains false, anyone following those instructions after a successful release will look in the wrong console and cannot publish the pending deployment; update the release documentation alongside this workflow migration.
AGENTS.md reference: AGENTS.md:L31-L35
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Done in 190f57d: the release instructions now point at the Central Portal (server id central, publish the pending deployment at https://central.sonatype.com/publishing/deployments since autoRelease is false).
The v7 release workflow publishes with central-publishing-maven-plugin (server id `central`); the OSSRH staging console the README referred to is gone. autoRelease stays false, so the pending deployment still has to be published by hand, on the Portal. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
GitHub runners now ship Maven 3.10.0 (image
ubuntu24/20261004and later). This PR aligns the project with MetricsHub/jflat and MetricsHub/simple-http-java.What changed
metricshub/workflowsv4 → v7 (build, deploy and release). The inputs are unchanged.https://central.sonatype.comas an origin of servercentral(Declare Central as an origin of server central for Maven 3.10 workflows#36).oss-parentis already 5.Validation
Maven Deployrun onmain:central-publishing:publishends in BUILD SUCCESS;🤖 Generated with Claude Code