Bump com.microsoft.sqlserver:mssql-jdbc from 13.3.1.jre11-preview to 13.3.2.jre11-preview

[dependabot]

Bumps com.microsoft.sqlserver:mssql-jdbc from 13.3.1.jre11-preview to 13.3.2.jre11-preview.

Release notes

Sourced from com.microsoft.sqlserver:mssql-jdbc's releases.

[13.3.2] Preview Release

Added

• Add VECTOR(FLOAT16) Subtype Support #2899Expand commentComment on line R10Resolved What was added: Introduced support for the VECTOR(FLOAT16) subtype, including feature negotiation and IEEE-754 compliant serialization/deserialization between Java Float[] and half-precision wire format. Who benefits: Applications building AI, embeddings, and vector search workloads that require reduced memory footprint and network payload. Impact: Enables efficient float16 vector storage and transmission while preserving backward compatibility and the existing Java programming model.

• Add prepareMethod=none Execution Path#2890 What was added: New prepareMethod=none option that forces literal parameter substitution with SQL batch execution, bypassing server-side prepared statement handles (sp_prepexec / sp_prepare). Who benefits: Applications preferring SQL Server–managed plan caching without driver-managed prepared handle reuse. Impact: Executes prepared statements as plain SQL batches, maintaining connection-level temp tables and providing a simplified alternative execution model while leaving the default behavior unchanged.

• Statement-Level Performance Logger Metrics#2885 What was added: Extended Performance Logger to capture detailed execution metrics for Statement and PreparedStatement (REQUEST_BUILD, FIRST_SERVER_RESPONSE, PREPARE, PREPEXEC, EXECUTE). Who benefits: Developers and performance engineers analyzing execution timing and driver behavior. Impact: Provides granular observability across all statement execution paths with minimal overhead.

• StateMachineTest Framework for JUnit 5#2887 What was added: Lightweight, seed-reproducible state-machine testing framework for randomized JDBC state exploration. Who benefits: Driver maintainers and CI stability efforts. Impact: Improves edge-case detection with reproducible failures without third-party dependencies.

• Add AI-Assisted Development Context Files#2882 What was added: ARCHITECTURE.md, GLOSSARY.md, and PATTERNS.md to guide AI-assisted development. Who benefits: Contributors using AI coding assistants. Impact: Improves code consistency and productivity by documenting architecture and established design patterns.

• Enhance Code Coverage (CallableStatement, DatabaseMetaData, PreparedStatement)#2875 What was added: Expanded unit and integration test coverage for key driver components including SQLServerCallableStatement, SQLServerDatabaseMetaData, and SQLServerPreparedStatement. Who benefits: Driver maintainers and users relying on stable metadata, statement execution, and callable behavior. Impact: Improves regression detection and long-term stability.

• New Bug Regression Tests in JUnit#2888 What was added: Migrated legacy FX regression tests (37 scenarios) covering statement execution, ResultSet behavior, batching, cursors, and transaction flows into JUnit with full behavioral parity. Who benefits: Contributors and CI validation pipelines. Impact: Achieves complete FX regression coverage with reproducible execution paths and improved long-term reliability.

Changed

• Remove ADAL Dependency – Migrate Windows AAD Integrated Auth to MSQA APIs#2864 What was changed: Replaced deprecated ADAL-based adalsql.dll flow with MSQA (mssql-auth.dll, MSAL C++). Who benefits: Users of Windows Active Directory Integrated Authentication. Impact: Fully removes legacy ADAL dependency, aligns with Microsoft deprecation guidance, and modernizes authentication architecture.

• Refactor DatabaseMetaData.getColumns() to use sp_columns_170 with fallback#2883 What was changed: getColumns() now prefers sp_columns_170 (SQL Server 2025) for accurate metadata on newer types such as VECTOR and enhanced JSON, with automatic fallback to sp_columns_100. Who benefits: Applications performing schema discovery against SQL Server 2025 and Azure environments. Impact: Ensures correct metadata for new engine features while preserving backward compatibility with older SQL Server versions.

... (truncated)

Commits

• See full diff in compare view

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 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 <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)