Release 2.16.0 - #70
Merged
Merged
Conversation
Moves the twelve version locations off SNAPSHOT. This is the first non-SNAPSHOT version this repository has ever published. Every prior release -- 2.14.0, 2.15.0, 2.15.1 -- was tagged as a SNAPSHOT, which is why the nexus-staging defect fixed in #58 went unnoticed for so long: it only fires on a release version, and no release version had ever run. Verified against a local file repository at this version, the case that used to fail on the parent pom with both modules skipped: deploy:3.1.2:deploy (default-deploy) @ cfparser deploy:3.1.2:deploy (default-deploy) @ cfml.dictionary deploy:3.1.2:deploy (default-deploy) @ cfml.parsing producing all nine artifacts -- the parent pom plus a jar, sources jar, javadoc jar and pom for each module. That exercises #58 and #60 together. 326 tests, ./gradlew build, class file major version 65.
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.
Moves the twelve version locations off SNAPSHOT. Nothing but version strings changes.
The first real release this repository has had
Every prior tag —
2.14.0-SNAPSHOT,2.15.0-SNAPSHOT,2.15.1-SNAPSHOT— was a SNAPSHOT. That is why thenexus-stagingdefect fixed in #58 survived since2.5.4-snapshot: it only fires on a release version, and a release version had never run. The workflow's tag trigger has therefore never actually published anything.So this release is also the first real exercise of that fix.
Verified at a release version
The case that previously failed on the parent pom with both library modules
SKIPPED, run against a local file repository:producing all nine artifacts:
That exercises #58 (deploy routes through
maven-deploy-plugin) and #60 (sources and javadoc attach) together, at the version shape both were broken for. The parent pom is present, whichCLAUDE.mdflags as the artifact consumers resolvingcfml.parsingcannot do without.All twelve locations
mvn versions:set -DnewVersion=2.16.0build.gradle, 2 ×gradle.propertiescfml.parsing/README.md,cfml.dictionary/README.md, rootREADME.mdreplaceratprepare-packagecfml.cli/README.md, rootREADME.mdversions:setexamplegrepreads2.16.0throughout andmvn packageafterwards leaves the tree clean.Verification
./gradlew buildjavapreports class file major version 65 (Java 21)cfml.parsing-2.16.0.jar/cfml.dictionary-2.16.0.jarAfter merging
Creating the GitHub release tagged
2.16.0mints the tag, firesmaven-publish.yml, and carries the notes. I cannot push tags from this environment — the egress proxy returns 403 on tag refs — so that step is yours.Master should then move to
2.16.1-SNAPSHOT, and CFLint's two pins to2.16.0. I can open both once the release is out.Generated by Claude Code