Cut new release 3.3.3

Recovers from the broken 3.3.2 release on Maven Central (#1431). PR #1432
fixed the source-side cause; this PR carries that fix to consumers via a
new release.

Changes:
  - Bump version 3.3.2 → 3.3.3 across all POMs, DriverUtil, and version
    assertions in tests.
  - Move NEXT_CHANGELOG entries into CHANGELOG under v3.3.3.
  - Reset NEXT_CHANGELOG to empty template.
  - Flip release freeze off (was on for 3.3.2).
  - Bump README install snippet.

Validation:
  - Built locally and verified assembly-uber/.flattened-pom.xml has zero
    <dependencies> and no <parent> — same shape as the working 3.3.1 POM.
  - End-to-end staging dry-run via v3.3.3-rc1: peco-databricks-jdbc workflow
    ran in staging-only mode, Sonatype validated the bundle on attempt 2,
    deployment a83f922f-9750-4a14-b697-a6005a6fc858 dropped after validation.
  - Live JDBC probe against the staged rc1 bundle resolved via Maven, loaded
    the driver, connected to dogfood, and round-tripped a SELECT — PROBE_OK.

Co-authored-by: Isaac
Signed-off-by: Vikrant Puppala <vikrant.puppala@databricks.com>

Author: vikrantpuppala

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Version Changelog
 
+## [v3.3.3] - 2026-04-29
+
+### Fixed
+- Fixed unresolvable Maven Central POM for the uber JAR. The published POM no longer declares a transitive dependency on the internal `databricks-jdbc-core` coordinate (which is not published to Maven Central), restoring resolution for downstream consumers (#1431).
+
 ## [v3.3.2] - 2026-04-27
 
 ### Added

NEXT_CHANGELOG.md

@@ -8,11 +8,6 @@
 
 ### Fixed
 
-- Fix unresolvable Maven Central POM for the uber JAR. The published POM no longer
-  declares a transitive dependency on the internal `databricks-jdbc-core` coordinate
-  (which is not published to Maven Central), restoring resolution for downstream
-  consumers (#1431).
-
 ---
 *Note: When making changes, please add your change under the appropriate section
 with a brief description.*

README.md

@@ -20,7 +20,7 @@ Add the following dependency to your `pom.xml`:
 <dependency>
   <groupId>com.databricks</groupId>
   <artifactId>databricks-jdbc</artifactId>
-  <version>3.3.2</version>
+  <version>3.3.3</version>
 </dependency>
 ```
 

assembly-thin/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>com.databricks</groupId>
         <artifactId>databricks-jdbc-parent</artifactId>
-        <version>3.3.2</version>
+        <version>3.3.3</version>
     </parent>
 
     <artifactId>databricks-jdbc-thin</artifactId>
@@ -51,7 +51,7 @@
         <dependency>
             <groupId>com.databricks</groupId>
             <artifactId>databricks-jdbc-core</artifactId>
-            <version>3.3.2</version>
+            <version>3.3.3</version>
         </dependency>
     </dependencies>
 

assembly-uber/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>com.databricks</groupId>
         <artifactId>databricks-jdbc-parent</artifactId>
-        <version>3.3.2</version>
+        <version>3.3.3</version>
     </parent>
 
     <artifactId>databricks-jdbc</artifactId>
@@ -51,7 +51,7 @@
         <dependency>
             <groupId>com.databricks</groupId>
             <artifactId>databricks-jdbc-core</artifactId>
-            <version>3.3.2</version>
+            <version>3.3.3</version>
         </dependency>
     </dependencies>
 

development/.release-freeze.json

@@ -1,3 +1,3 @@
 {
-  "freeze": true
+  "freeze": false
 }

jdbc-core/pom.xml

@@ -6,7 +6,7 @@
   <parent>
     <groupId>com.databricks</groupId>
     <artifactId>databricks-jdbc-parent</artifactId>
-    <version>3.3.2</version>
+    <version>3.3.3</version>
   </parent>
 
   <artifactId>databricks-jdbc-core</artifactId>

pom.xml

@@ -5,7 +5,7 @@
   <groupId>com.databricks</groupId>
   <artifactId>databricks-jdbc-parent</artifactId>
   <!-- This value may be modified by a release script to reflect the current version of the driver. -->
-  <version>3.3.2</version>
+  <version>3.3.3</version>
   <packaging>pom</packaging>
   <name>Databricks JDBC Parent</name>
   <description>Parent POM for Databricks JDBC Driver.</description>
@@ -63,7 +63,7 @@
     <build-helper-maven-plugin.version>3.6.1</build-helper-maven-plugin.version>
 
     <!-- Dependency Versions -->
-    <databricks-jdbc-version>3.3.2</databricks-jdbc-version>
+    <databricks-jdbc-version>3.3.3</databricks-jdbc-version>
     <arrow.version>18.3.0</arrow.version>
     <commons-lang3.version>3.18.0</commons-lang3.version>
     <commons-configuration.version>2.10.1</commons-configuration.version>

src/main/java/com/databricks/jdbc/common/util/DriverUtil.java

@@ -20,7 +20,7 @@
 public class DriverUtil {
 
   private static final JdbcLogger LOGGER = JdbcLoggerFactory.getLogger(DriverUtil.class);
-  private static final String DRIVER_VERSION = "3.3.2";
+  private static final String DRIVER_VERSION = "3.3.3";
   private static final String DRIVER_NAME = "oss-jdbc";
   private static final String JDBC_VERSION = "4.3";
 

src/test/java/com/databricks/jdbc/api/impl/DatabricksDatabaseMetaDataTest.java

@@ -828,7 +828,7 @@ public void testNullsAreSortedAtEnd() throws SQLException {
   @Test
   public void testGetDatabaseProductVersion() throws SQLException {
     String result = metaData.getDatabaseProductVersion();
-    assertEquals("3.3.2", result);
+    assertEquals("3.3.3", result);
   }
 
   @Test
@@ -840,7 +840,7 @@ public void testGetDriverName() throws SQLException {
   @Test
   public void testGetDriverVersion() throws SQLException {
     String result = metaData.getDriverVersion();
-    assertEquals("3.3.2", result);
+    assertEquals("3.3.3", result);
   }
 
   @Test