[maven-release-plugin] prepare for next development iteration

Author: tomaswolf

CHANGES.md

@@ -1,43 +1,3 @@
-# Apache MINA SSHD 2.18.0
-
-Changes since [version 2.17.1](./docs/changes/2.17.1.md):
-
-## Bug Fixes
-
-* [GH-743](https://github.com/apache/mina-sshd/issues/743) Ensure the Java `ServiceLoader` use a singleton `SftpFileSystemProvider`
-* [GH-879](https://github.com/apache/mina-sshd/issues/879) Close SSH channel gracefully on exception in port forwarding
-* Improve handling of repository paths in `sshd-git`.
-
-## New Features
-
-* [GH-892](https://github.com/apache/mina-sshd/issues/892) Align handling certificates without principals with OpenSSH 10.3
-
-Wildcard principals in host certificates are handled now.
-
-* Putty keys with non-ASCII passphrases
-
-The passphrase needs to be converted to a byte sequence to compute a decryption key for an encrypted private key. This
-conversion depends on the character encoding. Putty on Windows uses the ANSI codepage set when the key was generated.
-Apache MINA SSHD now tries multiple encodings in sequence: UTF-8, then the OS encoding, and finally ISO-8859-1 as a
-last-chance fallback.
-
-## Potential Compatibility Issues
-
-* [GH-892](https://github.com/apache/mina-sshd/issues/892) Align handling certificates without principals with OpenSSH 10.3
-
-OpenSSH 10.3 changed the way such certificates are handled; see the [OpenSSH 10.3 release notes](https://www.openssh.org/txt/release-10.3).
-In Apache MINA SSHD, there is a new flag `CoreModuleProperties.ALLOW_EMPTY_CERTIFICATE_PRINCIPALS` (by default `false`)
-that can be set on an `SshClient` or `SshServer` or also on a `Session` directly. If the value is `false`, certificates
-without principals are rejected as in OpenSSH 10.3; if it is `true`, such certificates are considered to match any
-user or host name as in OpenSSH < 10.3.
-
-Set the flag on an `SshClient` or `ClientSession` to determine the handling of host certificates. Set it on an
-`SshServer` or `ServerSession` to govern the handling of user certificates.
-
-## Major Code Re-factoring
-
-None.
-
 # Previous Versions
 
 * [Version 2.1.0 to 2.2.0](./docs/changes/2.2.0.md)
@@ -63,3 +23,21 @@ None.
 * [Version 2.15.0 to 2.16.0](./docs/changes/2.16.0.md)
 * [Version 2.16.0 to 2.17.0](./docs/changes/2.17.0.md)
 * [Version 2.17.0 to 2.17.1](./docs/changes/2.17.1.md)
+
+# Latest Version
+
+* **[Version 2.17.1 to 2.18.0](./docs/changes/2.18.0.md)**
+
+# Planned for Next Version
+
+## Bug Fixes
+
+
+## New Features
+
+
+## Potential Compatibility Issues
+
+
+## Major Code Re-factoring
+

assembly/pom.xml

@@ -22,7 +22,7 @@
     <parent>
         <groupId>org.apache.sshd</groupId>
         <artifactId>sshd</artifactId>
-        <version>2.18.0</version>
+        <version>2.19.0-SNAPSHOT</version>
     </parent>
 
     <artifactId>apache-sshd</artifactId>

docs/changes/2.18.0.md

@@ -0,0 +1,37 @@
+# Introduced in 2.18.0
+
+## Bug Fixes
+
+* [GH-743](https://github.com/apache/mina-sshd/issues/743) Ensure the Java `ServiceLoader` use a singleton `SftpFileSystemProvider`
+* [GH-879](https://github.com/apache/mina-sshd/issues/879) Close SSH channel gracefully on exception in port forwarding
+* Improve handling of repository paths in `sshd-git`.
+
+## New Features
+
+* [GH-892](https://github.com/apache/mina-sshd/issues/892) Align handling certificates without principals with OpenSSH 10.3
+
+Wildcard principals in host certificates are handled now.
+
+* Putty keys with non-ASCII passphrases
+
+The passphrase needs to be converted to a byte sequence to compute a decryption key for an encrypted private key. This
+conversion depends on the character encoding. Putty on Windows uses the ANSI codepage set when the key was generated.
+Apache MINA SSHD now tries multiple encodings in sequence: UTF-8, then the OS encoding, and finally ISO-8859-1 as a
+last-chance fallback.
+
+## Potential Compatibility Issues
+
+* [GH-892](https://github.com/apache/mina-sshd/issues/892) Align handling certificates without principals with OpenSSH 10.3
+
+OpenSSH 10.3 changed the way such certificates are handled; see the [OpenSSH 10.3 release notes](https://www.openssh.org/txt/release-10.3).
+In Apache MINA SSHD, there is a new flag `CoreModuleProperties.ALLOW_EMPTY_CERTIFICATE_PRINCIPALS` (by default `false`)
+that can be set on an `SshClient` or `SshServer` or also on a `Session` directly. If the value is `false`, certificates
+without principals are rejected as in OpenSSH 10.3; if it is `true`, such certificates are considered to match any
+user or host name as in OpenSSH < 10.3.
+
+Set the flag on an `SshClient` or `ClientSession` to determine the handling of host certificates. Set it on an
+`SshServer` or `ServerSession` to govern the handling of user certificates.
+
+## Major Code Re-factoring
+
+None.

pom.xml

@@ -27,7 +27,7 @@
 
     <groupId>org.apache.sshd</groupId>
     <artifactId>sshd</artifactId>
-    <version>2.18.0</version>
+    <version>2.19.0-SNAPSHOT</version>
     <name>Apache Mina SSHD</name>
     <packaging>pom</packaging>
     <inceptionYear>2008</inceptionYear>
@@ -67,7 +67,7 @@
         <connection>scm:git:https://gitbox.apache.org/repos/asf/mina-sshd.git</connection>
         <developerConnection>scm:git:https://gitbox.apache.org/repos/asf/mina-sshd.git</developerConnection>
         <url>https://github.com/apache/mina-sshd/tree/${project.scm.tag}</url>
-        <tag>sshd-2.18.0</tag>
+        <tag>master</tag>
     </scm>
 
     <properties>
@@ -80,7 +80,7 @@
 
 
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-        <project.build.outputTimestamp>2026-05-25T15:45:34Z</project.build.outputTimestamp>
+        <project.build.outputTimestamp>2026-05-25T15:48:29Z</project.build.outputTimestamp>
 
         <java.sdk.version>8</java.sdk.version>
         <javac.source>${java.sdk.version}</javac.source>

sshd-benchmarks/pom.xml

@@ -20,7 +20,7 @@
     <parent>
         <groupId>org.apache.sshd</groupId>
         <artifactId>sshd</artifactId>
-        <version>2.18.0</version>
+        <version>2.19.0-SNAPSHOT</version>
         <relativePath>..</relativePath>
     </parent>
 

sshd-cli/pom.xml

@@ -22,7 +22,7 @@
     <parent>
         <groupId>org.apache.sshd</groupId>
         <artifactId>sshd</artifactId>
-        <version>2.18.0</version>
+        <version>2.19.0-SNAPSHOT</version>
     </parent>
 
     <artifactId>sshd-cli</artifactId>

sshd-common/pom.xml

@@ -22,7 +22,7 @@
     <parent>
         <groupId>org.apache.sshd</groupId>
         <artifactId>sshd</artifactId>
-        <version>2.18.0</version>
+        <version>2.19.0-SNAPSHOT</version>
         <relativePath>..</relativePath>
     </parent>
 

sshd-contrib/pom.xml

@@ -22,7 +22,7 @@
     <parent>
         <groupId>org.apache.sshd</groupId>
         <artifactId>sshd</artifactId>
-        <version>2.18.0</version>
+        <version>2.19.0-SNAPSHOT</version>
     </parent>
 
     <!-- NOTE ::: NOTE ::: NOTE ::: NOTE ::: NOTE ::: NOTE ::: NOTE ::: NOTE :::

sshd-core/pom.xml

@@ -22,7 +22,7 @@
     <parent>
         <groupId>org.apache.sshd</groupId>
         <artifactId>sshd</artifactId>
-        <version>2.18.0</version>
+        <version>2.19.0-SNAPSHOT</version>
         <relativePath>..</relativePath>
     </parent>
 

sshd-git/pom.xml

@@ -22,7 +22,7 @@
     <parent>
         <groupId>org.apache.sshd</groupId>
         <artifactId>sshd</artifactId>
-        <version>2.18.0</version>
+        <version>2.19.0-SNAPSHOT</version>
     </parent>
 
     <artifactId>sshd-git</artifactId>