Repository navigation
CI: pin Maven 3.9.16 for Central deploy - #11
Merged
Merged
Conversation
Merged
michaeloffner
approved these changes
Oct 19, 2026
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
2 participants
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.
The release deploy for 3.0.0.8 would be rejected by Central as it stands.
Cause: on 2026-10-04 the GitHub
ubuntu-latestimage moved from Maven 3.9.16 to 3.10.0. With 3.10.0,central-publishing-maven-pluginleavesmaven-metadata-local.xmlin the staging dir, and Central rejects the bundle withBundle has content that does NOT have a .pom file. That's the same failure we fixed in lucee/extension-image#39 and in Lucee core. 3.0.0.4 (March) and the May snapshot deploys all ran on Maven 3.9.x.Fix: the
deployjob installs Maven 3.9.16 (sha512-verified, from Maven Central) before the extension and agentmvn deploysteps. It's the same step Lucee core uses. Build and test jobs are unchanged.--settings maven-settings.xmlis already passed on both deploy commands, so the credentials problem we found on Lucee 6.2 doesn't apply here.