Skip to content

Bump jlineVersion from 3.30.6 to 4.0.5#11808

Closed
dependabot[bot] wants to merge 1 commit intomaven-4.0.xfrom
dependabot/maven/maven-4.0.x/jlineVersion-4.0.5
Closed

Bump jlineVersion from 3.30.6 to 4.0.5#11808
dependabot[bot] wants to merge 1 commit intomaven-4.0.xfrom
dependabot/maven/maven-4.0.x/jlineVersion-4.0.5

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 18, 2026

Bumps jlineVersion from 3.30.6 to 4.0.5.
Updates org.jline:jline-reader from 3.30.6 to 4.0.5

Release notes

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

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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

... (truncated)

Commits
  • ee52d32 Merge pull request #1698 from jline/dependabot/github_actions/master/release-...
  • bd76b2b Merge pull request #1699 from jline/fix/maven3-compat
  • b33c819 fix: Clean up mvx command syntax in release workflow
  • d783438 fix: Guard release workflow against SNAPSHOT hint tags
  • aef6dbb fix: Revert build to Maven 3.9.x compatibility (fixes #1690)
  • b1e711d chore: Bump release-drafter/release-drafter from 6 to 7
  • 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
  • Additional commits viewable in compare view

Updates org.jline:jline-style from 3.30.6 to 4.0.5

Release notes

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

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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

... (truncated)

Commits
  • ee52d32 Merge pull request #1698 from jline/dependabot/github_actions/master/release-...
  • bd76b2b Merge pull request #1699 from jline/fix/maven3-compat
  • b33c819 fix: Clean up mvx command syntax in release workflow
  • d783438 fix: Guard release workflow against SNAPSHOT hint tags
  • aef6dbb fix: Revert build to Maven 3.9.x compatibility (fixes #1690)
  • b1e711d chore: Bump release-drafter/release-drafter from 6 to 7
  • 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
  • Additional commits viewable in compare view

Updates org.jline:jline-builtins from 3.30.6 to 4.0.5

Release notes

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

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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

... (truncated)

Commits
  • ee52d32 Merge pull request #1698 from jline/dependabot/github_actions/master/release-...
  • bd76b2b Merge pull request #1699 from jline/fix/maven3-compat
  • b33c819 fix: Clean up mvx command syntax in release workflow
  • d783438 fix: Guard release workflow against SNAPSHOT hint tags
  • aef6dbb fix: Revert build to Maven 3.9.x compatibility (fixes #1690)
  • b1e711d chore: Bump release-drafter/release-drafter from 6 to 7
  • 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
  • Additional commits viewable in compare view

Updates org.jline:jline-console from 3.30.6 to 4.0.5

Release notes

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

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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

... (truncated)

Commits
  • ee52d32 Merge pull request #1698 from jline/dependabot/github_actions/master/release-...
  • bd76b2b Merge pull request #1699 from jline/fix/maven3-compat
  • b33c819 fix: Clean up mvx command syntax in release workflow
  • d783438 fix: Guard release workflow against SNAPSHOT hint tags
  • aef6dbb fix: Revert build to Maven 3.9.x compatibility (fixes #1690)
  • b1e711d chore: Bump release-drafter/release-drafter from 6 to 7
  • 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
  • Additional commits viewable in compare view

Updates org.jline:jline-console-ui from 3.30.6 to 4.0.5

Release notes

Sourced from org.jline:jline-console-ui's releases.

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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

... (truncated)

Commits
  • ee52d32 Merge pull request #1698 from jline/dependabot/github_actions/master/release-...
  • bd76b2b Merge pull request #1699 from jline/fix/maven3-compat
  • b33c819 fix: Clean up mvx command syntax in release workflow
  • d783438 fix: Guard release workflow against SNAPSHOT hint tags
  • aef6dbb fix: Revert build to Maven 3.9.x compatibility (fixes #1690)
  • b1e711d chore: Bump release-drafter/release-drafter from 6 to 7
  • 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
  • Additional commits viewable in compare view

Updates org.jline:jline-terminal from 3.30.6 to 4.0.5

Release notes

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

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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

... (truncated)

Commits
  • ee52d32 Merge pull request #1698 from jline/dependabot/github_actions/master/release-...
  • bd76b2b Merge pull request #1699 from jline/fix/maven3-compat
  • b33c819 fix: Clean up mvx command syntax in release workflow
  • d783438 fix: Guard release workflow against SNAPSHOT hint tags
  • aef6dbb fix: Revert build to Maven 3.9.x compatibility (fixes #1690)
  • b1e711d chore: Bump release-drafter/release-drafter from 6 to 7
  • 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
  • Additional commits viewable in compare view

Updates org.jline:jline-terminal-ffm from 3.30.6 to 4.0.5

Release notes

Sourced from org.jline:jline-terminal-ffm's releases.

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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

... (truncated)

Commits
  • ee52d32 Merge pull request #1698 from jline/dependabot/github_actions/master/release-...
  • bd76b2b Merge pull request #1699 from jline/fix/maven3-compat
  • b33c819 fix: Clean up mvx command syntax in release workflow
  • d783438 fix: Guard release workflow against SNAPSHOT hint tags
  • aef6dbb fix: Revert build to Maven 3.9.x compatibility (fixes #1690)
  • b1e711d chore: Bump release-drafter/release-drafter from 6 to 7
  • 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
  • Additional commits viewable in compare view

Updates org.jline:jline-terminal-jni from 3.30.6 to 4.0.5

Release notes

Sourced from org.jline:jline-terminal-jni's releases.

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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

... (truncated)

Commits
  • ee52d32 Merge pull request #1698 from jline/dependabot/github_actions/master/release-...
  • bd76b2b Merge pull request #1699 from jline/fix/maven3-compat
  • b33c819 fix: Clean up mvx command syntax in release workflow
  • d783438 fix: Guard release workflow against SNAPSHOT hint tags
  • aef6dbb fix: Revert build to Maven 3.9.x compatibility (fixes #1690)
  • b1e711d chore: Bump release-drafter/release-drafter from 6 to 7
  • 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
  • Additional commits viewable in compare view

Updates org.jline:jline-native from 3.30.6 to 4.0.5

Release notes

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

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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

... (truncated)

Commits
  • ee52d32 Merge pull request #1698 from jline/dependabot/github_actions/master/release-...
  • bd76b2b Merge pull request #1699 from jline/fix/maven3-compat
  • b33c819 fix: Clean up mvx command syntax in release workflow
  • d783438 fix: Guard release workflow against SNAPSHOT hint tags
  • aef6dbb fix: Revert build to Maven 3.9.x compatibility (fixes #1690)
  • b1e711d chore: Bump release-drafter/release-drafter from 6 to 7
  • 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
  • Additional commits viewable in compare view

Updates org.jline:jansi-core from 3.30.6 to 4.0.5

Release notes

Sourced from org.jline:jansi-core's releases.

JLine 4.0.5

Merge pull request #1698 from jline/dependabot/github_actions/master/release-drafter/release-drafter-7

chore: Bump release-drafter/release-drafter from 6 to 7

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. (...

    Description has been truncated

@dependabot
Bump jlineVersion from 3.30.6 to 4.0.5
c19c006 
Bumps `jlineVersion` from 3.30.6 to 4.0.5.

Updates `org.jline:jline-reader` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

Updates `org.jline:jline-style` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

Updates `org.jline:jline-builtins` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

Updates `org.jline:jline-console` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

Updates `org.jline:jline-console-ui` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

Updates `org.jline:jline-terminal` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

Updates `org.jline:jline-terminal-ffm` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

Updates `org.jline:jline-terminal-jni` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

Updates `org.jline:jline-native` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

Updates `org.jline:jansi-core` from 3.30.6 to 4.0.5
- [Release notes](https://github.com/jline/jline3/releases)
- [Commits](jline/jline3@jline-3.30.6...4.0.5)

---
updated-dependencies:
- dependency-name: org.jline:jline-reader
  dependency-version: 4.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.jline:jline-style
  dependency-version: 4.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.jline:jline-builtins
  dependency-version: 4.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.jline:jline-console
  dependency-version: 4.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.jline:jline-console-ui
  dependency-version: 4.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.jline:jline-terminal
  dependency-version: 4.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.jline:jline-terminal-ffm
  dependency-version: 4.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.jline:jline-terminal-jni
  dependency-version: 4.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.jline:jline-native
  dependency-version: 4.0.5
  dependency-type: direct:development
  update-type: version-update:semver-major
- dependency-name: org.jline:jansi-core
  dependency-version: 4.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file mvn40 labels Mar 18, 2026
@dependabot dependabot bot mentioned this pull request Mar 18, 2026
Closed
@guylabs guylabs mentioned this pull request Mar 18, 2026
Open
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 19, 2026

Superseded by #11815.

@dependabot dependabot bot closed this Mar 19, 2026
@dependabot dependabot bot deleted the dependabot/maven/maven-4.0.x/jlineVersion-4.0.5 branch March 19, 2026 01:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file mvn40

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants