potiuk commented on PR #54194:
URL: https://github.com/apache/airflow/pull/54194#issuecomment-3161189034
I was thinking of ways we could handle it in the future after our last
discussion about newsfragments. I think (again) newsfragments is not a good
solution - because they basically do not solve THIS problem you see now.
But what we could do rather "easily" is to have a way to mark (for example
with a commant in pyproject.toml) that when preparing documentation for release
we could automatically bump it to the next version after the release is
prepared. For example:
```
"apache-airlflow-provider-common-sql>1.27.4", # bump this to next
version when releasing because of #NUM_PR
```
If we keep it in the code between releases, that could avoid having to bump
version earlier, and the "prepare-documentation" step could be extended by an
extra step at the end. Something like:
> The snowflake provider is marked to use new version of commons-sql (bumped
to 1.27.5). Current version is 1.27.4. Do you want to bump the dependency
version to 1.27.5 ?
That could make it easier - you would not have to remember that we need to
bump it. But it would require some explanation to contributors and care at the
review time to make sure such comment is added.
--
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]
