Skip to content

Update metricshub/workflows to v7 - #139

Merged
bertysentry merged 2 commits into
mainfrom
update/oss-parent-5-workflows-v7
Oct 8, 2026
Merged

bertysentry merged 2 commits into
mainfrom
update/oss-parent-5-workflows-v7

Conversation

@NassimBtk

Copy link
Copy Markdown
Collaborator

GitHub runners now ship Maven 3.10.0 (image ubuntu24/20261004 and later). This PR aligns the project with MetricsHub/jflat and MetricsHub/simple-http-java.

What changed

  • metricshub/workflows v4 → v7 (build, deploy and release). The inputs are unchanged.
  • The site is already on Doxia 2, so it is not changed.
  • oss-parent is already 5.

Validation

  • jflat and simple-http-java use the same v7 workflows. Their deploys on Maven 3.10.0 end in BUILD SUCCESS, and new snapshots are published on Central (the origin step passes).
  • This PR's CI runs the build (and the site) on the runner's Maven.
  • After the merge, check the first Maven Deploy run on main:
    • no "Not using credentials of server 'central'" warning in the deploy step;
    • central-publishing:publish ends in BUILD SUCCESS;
    • a new snapshot timestamp appears on Central.

🤖 Generated with Claude Code

- .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>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-08T16:46:49.716467Z 190f57d New commits
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>
@bertysentry
bertysentry merged commit aec89ee into main Oct 8, 2026
4 checks passed
@bertysentry
bertysentry deleted the update/oss-parent-5-workflows-v7 branch October 8, 2026 16:56
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.

2 participants