Conversation
Bumps [org.apache.maven.plugins:maven-deploy-plugin](https://github.com/apache/maven-deploy-plugin) from 3.1.2 to 3.1.3. - [Release notes](https://github.com/apache/maven-deploy-plugin/releases) - [Commits](apache/maven-deploy-plugin@maven-deploy-plugin-3.1.2...maven-deploy-plugin-3.1.3) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-deploy-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
mergify bot
added a commit
that referenced
this pull request
Mar 23, 2026
Bumps `jline.version` from 3.30.6 to 4.0.7. Updates `org.jline:jline-terminal` from 3.30.6 to 4.0.7 Release notes *Sourced from [org.jline:jline-terminal's releases](https://github.com/jline/jline3/releases).* > JLine 4.0.7 > ----------- > > 🐛 Bug Fixes > ----------- > > * Suppress dumb terminal warning when no streams are TTYs ([#1703](https://redirect.github.com/jline/jline3/pull/1703)) [`@gnodet`](https://github.com/gnodet) > + In CI environments (like GitHub Actions), the "Unable to create a system terminal" warning is no longer emitted when falling back to a dumb terminal is expected because no TTY is available > > **Full Changelog**: <jline/jline3@4.0.6...4.0.7> > > JLine 4.0.6 > ----------- > > 🔧 Build > ------- > > * Simplify versioning by using nisse property directly ([#1702](https://redirect.github.com/jline/jline3/pull/1702)) [`@gnodet`](https://github.com/gnodet) > > 📦 Dependency updates > -------------------- > > * Bump org.codehaus.mojo:exec-maven-plugin from 3.5.1 to 3.6.3 ([#1700](https://redirect.github.com/jline/jline3/pull/1700)) [`@dependabot`](https://github.com/dependabot) > > **Full Changelog**: <jline/jline3@4.0.5...4.0.6> > > JLine 4.0.5 > ----------- > > What's Changed > -------------- > > * fix: Revert build to Maven 3.9.x compatibility by [`@gnodet`](https://github.com/gnodet) in [jline/jline3#1699](https://redirect.github.com/jline/jline3/pull/1699) > * chore: Bump release-drafter/release-drafter from 6 to 7 by [`@dependabot`](https://github.com/dependabot)[bot] in [jline/jline3#1698](https://redirect.github.com/jline/jline3/pull/1698) > > **Full Changelog**: <jline/jline3@4.0.4...4.0.5> > > 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](https://redirect.github.com/jline/jline3/issues/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](https://redirect.github.com/jline/jline3/issues/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. ... (truncated) Commits * [`beabe4e`](jline/jline3@beabe4e) Merge pull request [#1703](https://redirect.github.com/jline/jline3/issues/1703) from jline/fix/suppress-dumb-terminal-warning-no-tty * [`b3bf72f`](jline/jline3@b3bf72f) fix: Suppress dumb terminal warning when no streams are TTYs * [`3ba42a8`](jline/jline3@3ba42a8) Merge pull request [#1700](https://redirect.github.com/jline/jline3/issues/1700) from jline/dependabot/maven/master/org.codehaus.mojo... * [`372a1bb`](jline/jline3@372a1bb) Merge pull request [#1702](https://redirect.github.com/jline/jline3/issues/1702) from jline/fix/simplify-nisse-setup * [`03b7d96`](jline/jline3@03b7d96) fix: Simplify versioning by using nisse property directly * [`8b6bd46`](jline/jline3@8b6bd46) chore: Bump org.codehaus.mojo:exec-maven-plugin from 3.5.1 to 3.6.3 * [`ee52d32`](jline/jline3@ee52d32) Merge pull request [#1698](https://redirect.github.com/jline/jline3/issues/1698) from jline/dependabot/github\_actions/master/release-... * [`bd76b2b`](jline/jline3@bd76b2b) Merge pull request [#1699](https://redirect.github.com/jline/jline3/issues/1699) from jline/fix/maven3-compat * [`b33c819`](jline/jline3@b33c819) fix: Clean up mvx command syntax in release workflow * [`d783438`](jline/jline3@d783438) fix: Guard release workflow against SNAPSHOT hint tags * Additional commits viewable in [compare view](jline/jline3@jline-3.30.6...4.0.7) Updates `org.jline:jline-reader` from 3.30.6 to 4.0.7 Release notes *Sourced from [org.jline:jline-reader's releases](https://github.com/jline/jline3/releases).* > JLine 4.0.7 > ----------- > > 🐛 Bug Fixes > ----------- > > * Suppress dumb terminal warning when no streams are TTYs ([#1703](https://redirect.github.com/jline/jline3/pull/1703)) [`@gnodet`](https://github.com/gnodet) > + In CI environments (like GitHub Actions), the "Unable to create a system terminal" warning is no longer emitted when falling back to a dumb terminal is expected because no TTY is available > > **Full Changelog**: <jline/jline3@4.0.6...4.0.7> > > JLine 4.0.6 > ----------- > > 🔧 Build > ------- > > * Simplify versioning by using nisse property directly ([#1702](https://redirect.github.com/jline/jline3/pull/1702)) [`@gnodet`](https://github.com/gnodet) > > 📦 Dependency updates > -------------------- > > * Bump org.codehaus.mojo:exec-maven-plugin from 3.5.1 to 3.6.3 ([#1700](https://redirect.github.com/jline/jline3/pull/1700)) [`@dependabot`](https://github.com/dependabot) > > **Full Changelog**: <jline/jline3@4.0.5...4.0.6> > > JLine 4.0.5 > ----------- > > What's Changed > -------------- > > * fix: Revert build to Maven 3.9.x compatibility by [`@gnodet`](https://github.com/gnodet) in [jline/jline3#1699](https://redirect.github.com/jline/jline3/pull/1699) > * chore: Bump release-drafter/release-drafter from 6 to 7 by [`@dependabot`](https://github.com/dependabot)[bot] in [jline/jline3#1698](https://redirect.github.com/jline/jline3/pull/1698) > > **Full Changelog**: <jline/jline3@4.0.4...4.0.5> > > 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](https://redirect.github.com/jline/jline3/issues/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](https://redirect.github.com/jline/jline3/issues/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. ... (truncated) Commits * [`beabe4e`](jline/jline3@beabe4e) Merge pull request [#1703](https://redirect.github.com/jline/jline3/issues/1703) from jline/fix/suppress-dumb-terminal-warning-no-tty * [`b3bf72f`](jline/jline3@b3bf72f) fix: Suppress dumb terminal warning when no streams are TTYs * [`3ba42a8`](jline/jline3@3ba42a8) Merge pull request [#1700](https://redirect.github.com/jline/jline3/issues/1700) from jline/dependabot/maven/master/org.codehaus.mojo... * [`372a1bb`](jline/jline3@372a1bb) Merge pull request [#1702](https://redirect.github.com/jline/jline3/issues/1702) from jline/fix/simplify-nisse-setup * [`03b7d96`](jline/jline3@03b7d96) fix: Simplify versioning by using nisse property directly * [`8b6bd46`](jline/jline3@8b6bd46) chore: Bump org.codehaus.mojo:exec-maven-plugin from 3.5.1 to 3.6.3 * [`ee52d32`](jline/jline3@ee52d32) Merge pull request [#1698](https://redirect.github.com/jline/jline3/issues/1698) from jline/dependabot/github\_actions/master/release-... * [`bd76b2b`](jline/jline3@bd76b2b) Merge pull request [#1699](https://redirect.github.com/jline/jline3/issues/1699) from jline/fix/maven3-compat * [`b33c819`](jline/jline3@b33c819) fix: Clean up mvx command syntax in release workflow * [`d783438`](jline/jline3@d783438) fix: Guard release workflow against SNAPSHOT hint tags * Additional commits viewable in [compare view](jline/jline3@jline-3.30.6...4.0.7) Updates `org.jline:jline-terminal-jni` from 3.30.6 to 4.0.7 Release notes *Sourced from [org.jline:jline-terminal-jni's releases](https://github.com/jline/jline3/releases).* > JLine 4.0.7 > ----------- > > 🐛 Bug Fixes > ----------- > > * Suppress dumb terminal warning when no streams are TTYs ([#1703](https://redirect.github.com/jline/jline3/pull/1703)) [`@gnodet`](https://github.com/gnodet) > + In CI environments (like GitHub Actions), the "Unable to create a system terminal" warning is no longer emitted when falling back to a dumb terminal is expected because no TTY is available > > **Full Changelog**: <jline/jline3@4.0.6...4.0.7> > > JLine 4.0.6 > ----------- > > 🔧 Build > ------- > > * Simplify versioning by using nisse property directly ([#1702](https://redirect.github.com/jline/jline3/pull/1702)) [`@gnodet`](https://github.com/gnodet) > > 📦 Dependency updates > -------------------- > > * Bump org.codehaus.mojo:exec-maven-plugin from 3.5.1 to 3.6.3 ([#1700](https://redirect.github.com/jline/jline3/pull/1700)) [`@dependabot`](https://github.com/dependabot) > > **Full Changelog**: <jline/jline3@4.0.5...4.0.6> > > JLine 4.0.5 > ----------- > > What's Changed > -------------- > > * fix: Revert build to Maven 3.9.x compatibility by [`@gnodet`](https://github.com/gnodet) in [jline/jline3#1699](https://redirect.github.com/jline/jline3/pull/1699) > * chore: Bump release-drafter/release-drafter from 6 to 7 by [`@dependabot`](https://github.com/dependabot)[bot] in [jline/jline3#1698](https://redirect.github.com/jline/jline3/pull/1698) > > **Full Changelog**: <jline/jline3@4.0.4...4.0.5> > > 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](https://redirect.github.com/jline/jline3/issues/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](https://redirect.github.com/jline/jline3/issues/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. ... (truncated) Commits * [`beabe4e`](jline/jline3@beabe4e) Merge pull request [#1703](https://redirect.github.com/jline/jline3/issues/1703) from jline/fix/suppress-dumb-terminal-warning-no-tty * [`b3bf72f`](jline/jline3@b3bf72f) fix: Suppress dumb terminal warning when no streams are TTYs * [`3ba42a8`](jline/jline3@3ba42a8) Merge pull request [#1700](https://redirect.github.com/jline/jline3/issues/1700) from jline/dependabot/maven/master/org.codehaus.mojo... * [`372a1bb`](jline/jline3@372a1bb) Merge pull request [#1702](https://redirect.github.com/jline/jline3/issues/1702) from jline/fix/simplify-nisse-setup * [`03b7d96`](jline/jline3@03b7d96) fix: Simplify versioning by using nisse property directly * [`8b6bd46`](jline/jline3@8b6bd46) chore: Bump org.codehaus.mojo:exec-maven-plugin from 3.5.1 to 3.6.3 * [`ee52d32`](jline/jline3@ee52d32) Merge pull request [#1698](https://redirect.github.com/jline/jline3/issues/1698) from jline/dependabot/github\_actions/master/release-... * [`bd76b2b`](jline/jline3@bd76b2b) Merge pull request [#1699](https://redirect.github.com/jline/jline3/issues/1699) from jline/fix/maven3-compat * [`b33c819`](jline/jline3@b33c819) fix: Clean up mvx command syntax in release workflow * [`d783438`](jline/jline3@d783438) fix: Guard release workflow against SNAPSHOT hint tags * Additional commits viewable in [compare view](jline/jline3@jline-3.30.6...4.0.7) 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) --- 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 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)
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
1 participant
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.
Bumps org.apache.maven.plugins:maven-deploy-plugin from 3.1.2 to 3.1.3.
Release notes
Sourced from org.apache.maven.plugins:maven-deploy-plugin's releases.
Commits
96bc864[maven-release-plugin] prepare release maven-deploy-plugin-3.1.300c14adRemove deprecation warning:07948ea[MDEPLOY-320] Simplify and unify message (#64)14cc4c3[MDEPLOY-311] Consider packaging in deploy-file mojo (#71)c814011[MDEPLOY-322] Use parent POM 43 (#74)23cdae6[MDEPLOY-319] Remove unfinished test - MDEPLOY-318-invalid-pomac740a7[MDEPLOY-319] Cleanup of test codeda2ad90Build with Maven4 (#57)6962699Bump resolverVersion from 1.9.18 to 1.9.20 (#55)ec081cf[maven-release-plugin] prepare for next development iterationDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)