dependabot[bot] opened a new pull request, #802: URL: https://github.com/apache/aries/pull/802
Bumps [org.jline:jline](https://github.com/jline/jline3) from 4.0.2 to 4.0.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jline/jline3/releases";>org.jline:jline's releases</a>.</em></p> <blockquote> <h2>JLine 4.0.4</h2> <h2>Bug Fixes</h2> <ul> <li>Disable grapheme cluster mode probe (DECRQM) on Windows <code>PosixSysTerminal</code> to prevent escape sequence <code>[?2027$p</code> from leaking into subprocess output on Cygwin/MSYSTEM environments (<a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a>) <ul> <li>This is a follow-up to the 4.0.3 fix which was insufficient — the <code>isSystemStream()</code> check was unreliable on Windows MSYSTEM environments</li> </ul> </li> </ul> <h2>Full Changelog</h2> <p><a href="https://github.com/jline/jline3/compare/4.0.3...4.0.4";>https://github.com/jline/jline3/compare/4.0.3...4.0.4</a></p> <h2>JLine 4.0.3</h2> <p>Bugfix release fixing output corruption on Windows when using Cygwin/MSYSTEM (Git Bash).</p> <h3>Bug Fixes</h3> <ul> <li><strong>Fix grapheme cluster probe corrupting output on Windows</strong> — On Windows with Cygwin/MSYSTEM (Git Bash), the DECRQM mode 2027 probe (<code>\e[?2027$p</code>) was written to a raw <code>FileDescriptor</code> (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 <code>ExecPty</code> output stream is not connected to a real terminal. Interactive Cygwin/MSYSTEM terminals that support mode 2027 are unaffected. (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jline/jline3/commit/2b64601ad9b61caca011c1cc8dc009a16b2695da";><code>2b64601</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a> from jline/fix/grapheme-probe-windows-2</li> <li><a href="https://github.com/jline/jline3/commit/75cfb61c6b8a3b557fd24c097dbae9d5f35f0bbc";><code>75cfb61</code></a> fix: Disable grapheme cluster probe on Windows PosixSysTerminal</li> <li><a href="https://github.com/jline/jline3/commit/edd28d281db006a6cbf08f1c9594d138802e706e";><code>edd28d2</code></a> fix: Skip grapheme cluster probe on Windows to prevent output corruption (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> <li>See full diff in <a href="https://github.com/jline/jline3/compare/4.0.2...4.0.4";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
