Prepare the 0.2.0 release - #4
Merged
Merged
Conversation
ChoMinGi
marked this pull request as ready for review
July 24, 2026 15:07
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
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.
What changed
0.2.0and fixes the reproducible-build timestamp.actionlintshell warning.Why
This is the release commit required before creating the signed
v0.2.0tag. Merging this PR does not publish to Maven Central; publication starts only when that tag is pushed.Checks
./mvnw -B -ntp clean verify./mvnw -B -ntp -Pquality -DskipTests -Djacoco.skip=true -Dmaven.javadoc.skip=true clean verifyactionlint0.2.0v0.2.0tag, GitHub release, or Maven Central coordinatesAfter merge, wait for
mainCI before creating and pushing the signed release tag.