duckdb-upgrade
A tool to easily upgrade duckdb databases from one version to another. It automates the process of exporting the contents of a DuckDB database and then importing them into a newer version of a DuckDB database.
Usage
This tool is available both through pip and Docker. Use one of the following commands to run it, or your preferred method to run Python packages or Docker images. These examples cover upgrading some DuckDB in the current directory to the latest version of the database.
via Pipx
$ uvx duckdb-upgrade example.duckdb
via Docker
$ docker run -v $(pwd):/data ghcr.io/mrflynn/duckdb-upgrade:latest /data/example.duckdb
Advanced Usage
You can also specify the target version you with to upgrade to using the -t flag.
For example, if you wish to upgrade some database to version 0.10.0, run the command
as follows:
$ duckdb-upgrade -t '0.10.0' example.duckdb
1 maintainer
Metadata
1 maintainer
Release files for duckdb-upgrade 0.18.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| duckdb_upgrade-0.18.0.tar.gz | 5.9 kB | With provenance | Details for duckdb_upgrade-0.18.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| duckdb_upgrade-0.18.0-py3-none-any.whl | Python 3 | none | any | Details for duckdb_upgrade-0.18.0-py3-none-any.whl |
Total release size: 13.3 kB
Release files / duckdb_upgrade-0.18.0.tar.gz
| Download URL | duckdb_upgrade-0.18.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6ad2e287cb00f22114d211bae457e65099b0a02ca69c6e65ad56cbed4cc6172
|
|
BLAKE2b-256 checksum How to use checksums |
8b5a40b4afe5e466603f1e7ddf8a5fe1b0b849bab48450063d42f61ff39c68cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / duckdb_upgrade-0.18.0-py3-none-any.whl
| Download URL | duckdb_upgrade-0.18.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
331f59cede007b42eddf51f6f81fbeed3bc695c208f6d9cc05f107364cf37db8
|
|
BLAKE2b-256 checksum How to use checksums |
cf93a0724ce89829ddd9e84167ae0e26ced65f366a138635d076a4563b5e0fa6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for duckdb-upgrade 0.18.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for duckdb_upgrade-0.18.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
