Skip to content

Release updates - #365

Merged
jmanico merged 7 commits into
mainfrom
release-updates
Dec 19, 2025
Merged

jmanico merged 7 commits into
mainfrom
release-updates

Conversation

@aalmiray

Copy link
Copy Markdown
Collaborator

Update build for pushing releases to Sonatype's Maven Central.
Additional updates include:

  • configuring the Maven wrapper
  • configuring the enforcer plugin
  • configuring JReleaser for releases
  • update build GH workflow
  • added release GH workflow

@kittylyst kittylyst left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

A couple of minor questions about the JDK versions in use, otherwise good.

uses: actions/setup-java@v5
with:
distribution: zulu
java-version: 11

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Just double-checking, but the plan is that we'll build on JDK 11 with source & target set to 8?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

That is correct, there are 2 artifacts built with release 8: empirism and java8-shim. The rest use release 10 as before.

Comment thread java10-shim/pom.xml
</description>

<properties>
<maven.compiler.release>10</maven.compiler.release>

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Why is this 10, rather than 11 as per the strategy clause?

Or is this just a quick fix to get this release out and prove out the pipeline, and this will moved to 11 on the next release?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

It was previously set to 10, I just moved configuration around but didn't change release values as that technically constitutes a bump in major compat. We can review this setting along with dependencies for the next release after the current one to get the CVE fix out the door.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

That's what I thought - thanks for confirming & I think this is GTG. 🚢 in my opinion!

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

#364 needs to be merged first

@melloware melloware 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.

Love this!!!

@jmanico
jmanico merged commit 16ce6bb into main Dec 19, 2025
3 checks passed
@jospint

jospint commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

GHA build failed.
Attempt to fix it #366
cc/ @jmanico

@jmanico
jmanico deleted the release-updates branch September 11, 2026 01:37
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.

5 participants