Bump org.jline:jline-reader from 3.30.6 to 4.0.4

[dependabot]

Bumps org.jline:jline-reader from 3.30.6 to 4.0.4.

Release notes

Sourced from org.jline:jline-reader's releases.

JLine 4.0.4

Bug Fixes

• Disable grapheme cluster mode probe (DECRQM) on Windows PosixSysTerminal to prevent escape sequence [?2027$p from leaking into subprocess output on Cygwin/MSYSTEM environments (#1696)
  • This is a follow-up to the 4.0.3 fix which was insufficient — the isSystemStream() check was unreliable on Windows MSYSTEM environments

Full Changelog

jline/jline3@4.0.3...4.0.4

JLine 4.0.3

Bugfix release fixing output corruption on Windows when using Cygwin/MSYSTEM (Git Bash).

Bug Fixes

• Fix grapheme cluster probe corrupting output on Windows — On Windows with Cygwin/MSYSTEM (Git Bash), the DECRQM mode 2027 probe (\e[?2027$p) was written to a raw FileDescriptor (stdout/stderr) rather than a real PTY device. When the output was piped (e.g. subprocess with captured output), this escape sequence leaked into the process output, corrupting downstream consumers. The probe is now skipped when the ExecPty output stream is not connected to a real terminal. Interactive Cygwin/MSYSTEM terminals that support mode 2027 are unaffected. (#1695)

JLine 4.0.2

Bugfix release fixing Maven 3/Gradle compatibility and JNI terminal provider issues.

Note: Users of 4.0.0 and 4.0.1 should upgrade to 4.0.2. Both prior releases had broken consumer POMs that prevented Maven 3 and Gradle from resolving JLine dependencies.

Bug Fixes

• Fix Maven 3/Gradle compatibility — Consumer POMs now use modelVersion 4.0.0 with no <parent> reference, making them consumable by Maven 3 and Gradle. Previously, child module POMs referenced jline-parent which used modelVersion 4.1.0, causing resolution failures. (#1691, #1694, fixes #1688, workaround for apache/maven#11772)
• Fix JNI terminal failing to load on JDK 21.0.10+ — Module.isNativeAccessEnabled() was backported to some JDK 21 builds (e.g. 21.0.10), causing a false UnsupportedOperationException since the method returns false even though JNI works without --enable-native-access. JNI native access restrictions are only enforced from JDK 24+, so the check is now skipped on earlier versions. (#1692, fixes #1689)

Dependency Updates

• Bump spotless-maven-plugin from 3.2.1 to 3.3.0
• Bump native-maven-plugin from 0.11.4 to 0.11.5
• Bump maven-shade-plugin from 3.6.0 to 3.6.2
• Bump maven-resources-plugin from 3.3.1 to 3.5.0

JLine 4.0.1

Merge pull request #1692 from jline/fix/jni-native-access-check-1689

fix: Skip JNI native access check on JDK < 24 (fixes #1689)

JLine 4.0.0

Breaking Changes

• Maven 4 requirement: Upgraded to POM model 4.1.0
• Java 11+ required: Raised minimum runtime requirement from Java 8 to Java 11
• JPMS migration: Complete Java Platform Module System migration with Java 24 support (#1374)
• JNA provider removed: Only JNI and FFM terminal providers remain
• Removed deprecated elements: All previously deprecated APIs removed (#1384)
• Standard Java SPI: Terminal providers now use standard Java ServiceLoader (#1523)

... (truncated)

Commits

• 2b64601 Merge pull request #1696 from jline/fix/grapheme-probe-windows-2
• 75cfb61 fix: Disable grapheme cluster probe on Windows PosixSysTerminal
• edd28d2 fix: Skip grapheme cluster probe on Windows to prevent output corruption (#1695)
• 2505581 Merge pull request #1694 from jline/fix/consumer-pom-flatten-location
• 397f434 fix: Move consumer POM flattening config to .mvn/maven.properties
• f6a7673 Merge pull request #1692 from jline/fix/jni-native-access-check-1689
• 9532659 fix: Skip JNI native access check on JDK < 24 (fixes #1689)
• 786a040 Merge pull request #1691 from jline/fix/consumer-pom-flatten
• dc4931b fix: Enable consumer POM flattening to fix Maven 3/Gradle compatibility (work...
• 4e7d7e1 Merge pull request #1687 from jline/dependabot/maven/master/org.apache.maven....
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)