Repository navigation
Release 1.5.15 - #64
Merged
Merged
Conversation
The last release, 1.5.14 in May, pins cfparser 2.15.0-SNAPSHOT -- a parser from March. Everything fixed since then exists only on master, so anyone using a released CFLint still hits the reported behaviour in #50 and #52 despite both being closed. This release carries cfparser 2.16.0, which fixes them: - arrow functions build a real AST, so they no longer silence every rule in the file (#52) - component-level static declarations no longer throw, taking the file with them (#50) - access modifiers accepted inside a static block (#50) - :: and ?. survive decompile instead of collapsing to a dot (#50) Verified at this version: 675 tests under both Maven and Gradle, and a deploy against a local file repository routing through maven-deploy-plugin to produce the jar, the -all fat jar and the pom.
Merged
ghedwards
added a commit
that referenced
this pull request
Sep 11, 2026
#70 set master to the fixed 1.5.15, but master already carried that version through #64 before an earlier release was called off, so the number has a history that matches nothing published. Nothing was ever released at 1.5.15; this moves to 1.5.16 instead. The cfparser pin moves to 2.16.2-SNAPSHOT for the same reason: 2.16.1-SNAPSHOT has been published more than once and no longer identifies a single build. Both declarations move together - pom.xml's cfparser.version property and the hardcoded coordinate in build.gradle. 675 tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Moves the two version locations off SNAPSHOT.
Why now
1.5.14, the last release, pins cfparser2.15.0-SNAPSHOT— a parser from March. Everything fixed since exists only on master, so anyone using a released CFLint still hits the reported behaviour in #50 and #52 despite both being closed.This release carries cfparser
2.16.0, which fixes them:(a, b) => a + bproduced the identifier chaina.ba + b, which derailed the walk and silenced every rule in the file.static x = 1;no longer throws NullPointerException, which used to abort the whole file —PARSE_ERROR, no results.static { }block, and the block is no longer discarded from the AST.::and?.survive decompile instead of collapsing to..a?.bbecominga.bchanged meaning — one yields null where the other throws.Also inherited: array slicing,
instanceOf, script-syntax tags, Lucee extensions, inline component definitions, correctedcfproperty/cfparamattribute sets, and elvis-operator precedence.Verified against the released parser
#52re-checked with a clean build resolvingcfml.parsing:2.16.0— the reporter's exact component, with and without the arrow function:mvn deployagainst a local file repository routes throughmaven-deploy-pluginand producescflint-1.5.15.jar,cflint-1.5.15-all.jarand the pomPublishing
publish.ymlfires onrelease: created, and since #57 also onworkflow_dispatch. Unlike cfparser's2.16.0, nothing has been published at1.5.15, so there is no duplicate-publish hazard either way.nexus-stagingsits inside thedeployprofile here rather than the main build, so it does not hijack the deploy phase — release publishing on this side already works, as1.5.14demonstrated.Known gap, not fixed here
The Maven deploy attaches no sources or javadoc jars — both plugins live in the
deployprofile the publish workflow never activates. Same cause as the cfparser issue fixed in its #61. Gradle builds them; Maven does not publish them. Out of scope for a version bump, and worth its own change.Generated by Claude Code