Skip to content

Build against Maven 4.0.0-rc-6 - #2027

Merged
slachiewicz merged 1 commit into
apache:masterfrom
slachiewicz:maven-4.0.0-rc-6
Aug 4, 2026
Merged

slachiewicz merged 1 commit into
apache:masterfrom
slachiewicz:maven-4.0.0-rc-6

Conversation

@slachiewicz

@slachiewicz slachiewicz commented Aug 4, 2026 •

Copy link
Copy Markdown
Member

4.0.0-rc-6 is released. This moves maven4Version to it and pins the same version explicitly in the Verify workflow, so CI no longer depends on the maven4-version default in maven-gh-actions-shared.

Verified: green on the fork before opening.

Move the Maven 4 version property to the current RC and pin the same
version explicitly in the Verify workflow, so CI does not depend on the
maven4-version default in maven-gh-actions-shared.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@gnodet gnodet left a comment

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.

Straightforward version bump from rc-5 to rc-6, following the established pattern (rc-3→rc-4 in 31cecc9, rc-4→rc-5 in b9d00c8). The CI pin in maven-verify.yml is a good addition — keeps CI aligned with the project property. All downstream ${maven4Version} references pick up the new value automatically.

This review was generated by an AI agent (Claude Code) and may contain inaccuracies. Please verify all suggestions before applying.

On behalf of gnodet

@slachiewicz
slachiewicz merged commit 478f77f into apache:master Aug 4, 2026
39 of 40 checks passed
@slachiewicz
slachiewicz deleted the maven-4.0.0-rc-6 branch August 4, 2026 12:33
@github-actions github-actions Bot added this to the 2.0.22 milestone Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants