Versioning

Each driver in the family is versioned and released independently. This page explains the model, the current versions, and how this documentation tracks releases.

Current versions

Driver	Database	Current version	What's new
ArpeMSSQL	Microsoft SQL Server	0.7.6	Release highlights
ArpePGSQL	PostgreSQL	0.4.7	Release highlights
ArpeOracle	Oracle	0.4.2	Release highlights
ArpeNetezza	IBM Netezza	0.3.7	Release highlights
ArpeTeradata	Teradata	0.3.5	Release highlights

Run the installer's --list for the authoritative, always-current set:

curl -fsSL https://raw.githubusercontent.com/arpe-io/adbc-drivers/main/install.sh | sh -s -- --list

The version model

• Semantic versioning. Each driver tags releases vMAJOR.MINOR.PATCH (e.g. v0.5.24). Drivers version on their own cadence — ArpeMSSQL being at 0.7.x while ArpeOracle is at 0.4.x is expected, not a mismatch.
• Check the installed version through ADBC GetInfo (driver version).
• Release tags map to download assets. Binaries are published on the adbc-drivers Releases page under a per-driver tag, arpe<db>-v<X.Y.Z> (e.g. arpeoracle-v0.3.9), each with a SHA256SUMS. The installer maps a load name + version to the matching asset.
• Pin a version at install time with --version X.Y.Z (-Version on Windows); the default is latest.

Handling version drift in these docs

This documentation site documents one current version per driver rather than keeping a browsable archive of every past release. Version-specific detail is conveyed three ways, consistently:

1. A version badge on each driver's landing page states the release these docs describe.
2. Inline Since vX.Y.Z notes flag options and features that were added or changed recently, so you can tell what your installed build supports. For example, ArpeOracle's OCI IAM token auth is marked since v0.2.0 and its OAuth2 / Entra ID login since v0.2.2.
3. A per-driver What's New page is the reader-facing version diff — what changed and when — so if you're on an older build you can see what upgrading gains you.