dbt-mysql
dbt-mysql copied to clipboard
dbeatty10
upgrade to support dbt-core v1.3.0
Background
The latest release cut for 1.3.0, dbt-core==1.3.0rc2 was published on October 3, 2022 (PyPI | Github). We are targeting releasing the official cut of 1.3.0 in time for the week of October 16 (in time for Coalesce conference).
We're trying to establish a following precedent w.r.t. minor versions: Partner adapter maintainers release their adapter's minor version within four weeks of the initial RC being released. Given the delay on our side in notifying you, we'd like to set a target date of November 7 (four weeks from today) for maintainers to release their minor version
| Timeframe | Date (intended) | Date (Actual) | Event |
|---|---|---|---|
| D - 3 weeks | Sep 21 | Oct 10 | dbt Labs informs maintainers of upcoming minor release |
| D - 2 weeks | Sep 28 | Sep 28 | core 1.3 RC is released |
| Day D | October 12 | Oct 12 | core 1.3 official is published |
| D + 2 weeks | October 26 | Nov 7 | dbt-adapter 1.3 is published |
How to upgrade
https://github.com/dbt-labs/dbt-core/discussions/6011 is an open discussion with more detailed information, and https://github.com/dbt-labs/dbt-core/issues/6040 is for keeping track of the community's progress on releasing 1.2.0
Below is a checklist of work that would enable a successful 1.2.0 release of your adapter.
- [ ] Python Models (if applicable)
- [ ] Incremental Materialization: cleanup and standardization
- [ ] More functional adapter tests to inherit
Support for dbt-core v1.3.0 would be great. Just wondering if there is any progress being made on this!
This issue has been partially addressed in an alpha version of dbt-mysql (v1.3.0a1).
While this release of the adapter is compatible with dbt-core 1.3 and supports basic functionality, we have not yet fully addressed the checklist items for full 1.3 support.
