ВЕРСИИ (18)

ci: publish holders with Fabric-compatible game range

ci: fix unterminated quote in version echo

Automated bump to version **3.53.2.0**.

Automated bump to version **3.53.1.0**.

modrinth body: document the public API + holder-driven engine upgrade Recasts the 'this mod is inert on Bukkit' framing into the two-path distinction: - Default path (DriverManager.getConnection): bundled driver wins, this mod is no-op. - Workaround path (MinecraftSqliteJdbc.connect / MinecraftMysqlJdbc.connect): child-first classloader gives consumers explicit access to this mod's driver, useful for newer engine features the server's bundled driver doesn't have. Adds API table + softdepend + code snippet so consumer plugin authors can wire it up. Cross-references Grim's wiki for the auto-detection integration.

api: child-first classloader workaround in MinecraftSqliteJdbc Bukkit/Spigot/Paper bundle sqlite-jdbc on the server's parent classloader. Plugin classloaders delegate parent-first, so any consumer plugin that does Class.forName("org.sqlite.JDBC") or DriverManager.getConnection always resolves to the bundled driver — installing this holder mod has no effect under default semantics, regardless of what's in plugins/. Verified empirically across paper-1.12.2 (engine 3.21.0 bundled) and paper-1.21.11 (engine 3.49.1.0 in libraries/) — the holder loads as a plugin but its driver class is never consulted, DriverManager registers only the bundled driver, sqlite_version() returns the bundled engine. This commit adds a public API class that gives consumers an explicit escape hatch: a child-first URLClassLoader pointing at this holder's own jar, parented to the platform classloader so org.sqlite.* must come from the holder jar (the parent chain has no org.sqlite). The Driver loaded from this classloader has a distinct class identity from the bundled copy, so DriverManager.getConnection still hits bundled but MinecraftSqliteJdbc.connect() returns a connection through the holder's engine. Verified on paper-1.12.2 in the same JVM: baseline DriverManager → engine 3.21.0 child-first holder API → engine 3.53.0 API surface: Connection connect(String url) Connection connect(String url, Properties properties) Driver driver() String engineVersion() String driverVersion() void eagerInit() void shutdown() Caveats are documented in the class javadoc — chiefly: stick to java.sql.* interfaces (the impl class org.sqlite.SQLiteConnection lives in the child-first classloader and won't down-cast across boundaries), DriverManager.getConnection won't pick this driver up (use connect() directly), and the native SQLite library is extracted twice when both bundled and holder are in use (one extraction per classloader). DEFAULT PATH IS UNCHANGED Consumer plugins that don't need a newer engine continue to use DriverManager.getConnection like always — they pick up the bundled driver and don't need to softdepend on this holder. Install this holder only on Fabric/NeoForge (no bundled driver) or when you specifically want a newer SQLite engine than what your server bundles. INTEGRATION Grim's SqliteBackend wires this in: probes for MinecraftSqliteJdbc at init, compares engineVersion() to the bundled, routes through the holder when it's strictly newer. Lets a Paper 1.8-1.12 server use modern UPSERT writers (which need engine 3.24+) by installing this mod. Implementation moved to a separate :api Gradle subproject with Java 8 toolchain so the API class compiles to bytecode runnable on every supported MC server. Root project keeps default toolchain to coexist with the neoforge-1.21 subproject's Java 21 requirement.

modrinth body: holder is functionally inert when bundled driver exists Tested empirically (paper-1.12.2 with engine 3.21.0 bundled, paper-1.21.11 with engine 3.49.1.0 in libraries/) — the bundled driver wins driver-class resolution every time, regardless of whether the holder is installed. Plugin classloaders delegate to the server parent classloader first; parent already holds org.sqlite.JDBC / com.mysql.cj.jdbc.Driver; holder's PluginClassLoader is never consulted; DriverManager only ever has the bundled driver registered. Body now states this directly so operators don't install the mod expecting it to upgrade their bundled driver. Holder remains useful on Fabric/NeoForge (no bundled) and Bukkit forks that strip the driver.

modrinth: managed body.md + auto-sync workflow Adds .modrinth/body.md as the source-of-truth for the Modrinth project body, and a separate workflow that PATCHes the project on every push that touches body.md. Description fixes don't have to wait for a version bump. Aligns with the body-sync pattern used in the four sibling holder repos (minecraft-{postgresql-jdbc,mysql-jdbc,mongodb-driver,jedis}).

Automated bump to version **3.53.0.0**.

Automated bump to version **3.51.3.0**.

Automated bump to version **3.51.2.0**.

Bump dependencies

Automated bump to version **3.51.0.0**.

Automated bump to version **3.50.3.0**.

Automated bump to version **3.50.2.0**.

Automated bump to version **3.50.1.0**.

Fix Neoforge 1.21+ support