Skip to content

Conversation

staticlibs
Copy link
Collaborator

DuckDB is using 3-part version number. Sometimes it may be necessary to make an updated JDBC release with the changes only in JDBC/JNI code keeping the engine version the same. For this it is proposed to add fourth component to version number for JDBC-specific changes. So the version is supposed to look like v1.2.2.0.

Testing: JAR bundling with 4-part version was tested in a separate repo.

DuckDB is using 3-part version number. Sometimes it may be necessary to
make an updated JDBC release with the changes only in JDBC/JNI code
keeping the engine version the same. For this it is proposed to add
fourth component to version number for JDBC-specific changes. So the
version is supposed to look like `v1.2.2.0`.

Testing: JAR bundling with 4-part version was tested in a separare repo.
@staticlibs staticlibs merged commit a42abde into duckdb:main Apr 10, 2025
2 checks passed
@staticlibs
Copy link
Collaborator Author

Merging without review as a workflow-only change.

@staticlibs staticlibs deleted the 4_part_version branch April 10, 2025 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant