| name | upgrade-duckdb-extension |
| description | Upgrade duckdb_opendalfs to a new DuckDB release. Use when the user asks to upgrade DuckDB, bump the duckdb submodule, sync to a new DuckDB tag, or update DuckDB and extension-ci-tools together. |
Upgrade duckdb_opendalfs to a new DuckDB release
DuckDB and extension-ci-tools must move together. OpenDAL is independently pinned and should only move when the target DuckDB version requires a compatibility fix. Then update CI metadata, build, format, and run the extension test.
Inputs
Confirm the target DuckDB release tag, for example v1.6.0, before making changes.
Workflow
Track these steps as a checklist and do not skip ahead:
- Fetch tags and pin the
duckdb submodule to tags/$TARGET.
- Pin
extension-ci-tools to the matching release tag or the release-compatible tag required by DuckDB.
- Upgrade the
opendal submodule to the latest upstream version.
- Run
make format-all.
- Build with
CMAKE_BUILD_PARALLEL_LEVEL=12 make reldebug.
- Run C++ unit tests with
build/reldebug/test/unittest and SQL tests with make test_reldebug.
- Update CHANGELOG.md, add a new release entry.
Current dependency model
duckdb: pinned to a DuckDB release tag.extension-ci-tools: pinned to the compatible DuckDB extension tooling release.opendal: independently pinned to the C++ binding revision used by this extension.
