You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the recommended process for upgrading duckdb and extension-ci-tools submodules? I have changed the duckdb stable version in .github/workflows/MainDistributionPipeline.yml as mentioned in README. I believe this will take care of the builds on the GitHub. For the local environment, do we have to pull the changes from the submodules explicitly?
The text was updated successfully, but these errors were encountered:
varunkumar
changed the title
Process of upgrading Duck version
Process for upgrading Duck version
Sep 12, 2024
the reusable workflow duckdb/extension-ci-tools/.github/workflows/_extension_distribution.yml for the duckdb-stable-build job should be set to latest tagged release
Can you please elaborate on this?
Changing the version uses: duckdb/extension-ci-tools/.github/workflows/[email protected]
to uses: duckdb/extension-ci-tools/.github/workflows/[email protected] is good enough right?
What is the recommended process for upgrading
duckdb
andextension-ci-tools
submodules? I have changed the duckdb stable version in.github/workflows/MainDistributionPipeline.yml
as mentioned in README. I believe this will take care of the builds on the GitHub. For the local environment, do we have to pull the changes from the submodules explicitly?The text was updated successfully, but these errors were encountered: