duckdb / duckdb/extension-template
Process for upgrading Duck version
- Dominant language
- Python
- Stars
- 290
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
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](https://github.com/duckdb/extension-template?tab=readme-ov-file#versioning-of-your-extension). 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?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the versioning section of the README and .github/workflows/MainDistributionPipeline.yml. Review how the duckdb and extension-ci-tools submodules are referenced, then check the local development instructions and existing issue discussion. Done means documenting the recommended upgrade steps for GitHub builds and the local environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100