vincbeck commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4509017255

   > > [@jscheffl](https://github.com/jscheffl) Not that I have anything 
against, but why are we doing a major release of `common.sql`? I see only my 
feature PR since last release, and it's definitely not a breaking change.
   > 
   > Oh, I needed a moment to triage backwards "how" this came. After a good 
sleep and a hard working day my memory is a bit dissolved from what I did 
yesterday but mechanics is as you nee in the published release notes of RC in 
https://airflow.staged.apache.org/docs/apache-airflow-providers-common-sql/2.0.0/changelog.html
 that there is a big fat warning banner about breaking change. This was in 
front of the changelog which by release manager mechanic the signal that a 
breaking change was added and this caused the major version bump.
   > 
   > But as you hinted... looking at the history from past providers release 
from 2026-05-05 in 
https://github.com/apache/airflow/pull/66424/changes#diff-67507f2803366fd3ff09a384dcb696bfd4a20ab1e75bb3e15f289c63e37b18edR28
 I need to acknowledge that re-reading the old state that by accident the 
braking change was actually missed 2 weeks ago in last providers release 1.36.0 
- actually this would have needed to be 2.0.0.
   > 
   > Due to the changelog and version mis-match... I assume it is fair to 
retro-major-bump the provider so that everybody in <= 1.36 sees there is a 
breaking change with warning. Would have been better last release cycle and 
this today we would have 2.1.0.
   > 
   > Hope it is okay to keep 2.0.0 :-D
   > 
   > (FYI [@vincbeck](https://github.com/vincbeck))
   
   Oh damn! I missed that! Sorry about that. I agree for bumping to major 
version at this cycle, better later than never ...


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to