potiuk commented on PR #54651: URL: https://github.com/apache/airflow/pull/54651#issuecomment-3239404527
cc: @eladkal . This is yet **another** example where we have to (when you prepare providers) do the following: a) update common.messaging to 2.0.0 b) update all providers that use common.messaging to be >= 2.0.0 There are two options for it: 1) This could be done **now** -> but this will cause the problematic changelog behaviours you complained about - i.e. the changelog type selection will not be taken into account. 2) You need to remember to do it when you prepare release documentation. Currently we have no information stored anywhere except this discussion here what to do with those providers. Seems that current consensus is that we should do "sudden death" - i.e what I described above (2.0.0 in common.messaging and >=2.0.0 in dependencies of providers that depend on common.messaging). I am not sure if there is another way of storing it - or just **remembering** that you have to do it is enough. Or maybe we can figure out a way how to replace "remembering" with some information stored in the repo. Currently we have no such information stored, what we should do is literally stored in this discussion. Maybe we might come up with some good ideas how to handle those cases better @gopidesupavan @amoghrajesh as well? -- 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]
