Prepare providers release 2026-01-13#60437
Conversation
|
@eladkal or @potiuk need some providers managers power knowledge - some providers I have marked with "Not docs only" and then the other fixes were hidden from classification such that docs only update is made. Others marked with docs only ( because of year change in NOTICE) were docs only but not rendered changelogs... for consistency do I need to make all providers with NOTICE changes being a release (forced) to distribute or shall I downgrade the "docs only" releases to the same that are just for NOTICE? |
dheerajturaga
left a comment
There was a problem hiding this comment.
Verified changes to edge3 and celery. Test failure was unrelated hence I attempted to rerun.
Sorry for late notice - I was away and disconnected last few days - and I am now struck with cold and trying to catch up :) Not sure if I understand :) -> but let me rephrase and see if I got it right:
Correct? If so - that's an interesting question - but I think the problem is that NOTICE change is not doc-only - it's a "Doc-only" changes are changes that only impact generated documentation - not the released package. In this case NOTICE change actually changes the released distribution so we should make it Misc. |
potiuk
left a comment
There was a problem hiding this comment.
Hmm. Sorry for doing that, but I think we should release literally all providers now - the NOTICE change is not really a "doc-only" change - it's a change that affects released distributions (NOTICE is part of meta-data) and I think "all" providers should be rleeased.
6542cbf to
be92c96
Compare
That was a bit too early. I need to officially cut the release (not the docs only) and then will call for VOTE for testing! |
|
@potiuk ditched previous work and re-generated ALL from scratch - second pass review please! |
* Prepare providers release 2026-01-13 * Upgrade common-compat in core as well * Make dev and optional dependencies consistent * Revert provider bump on core
* Prepare providers release 2026-01-13 * Upgrade common-compat in core as well * Make dev and optional dependencies consistent * Revert provider bump on core
* Prepare providers release 2026-01-13 * Upgrade common-compat in core as well * Make dev and optional dependencies consistent * Revert provider bump on core
* Prepare providers release 2026-01-13 * Upgrade common-compat in core as well * Make dev and optional dependencies consistent * Revert provider bump on core
* Prepare providers release 2026-01-13 * Upgrade common-compat in core as well * Make dev and optional dependencies consistent * Revert provider bump on core
Was generative AI tooling used to co-author this PR?
...at least as long as Breeze is not using AI to support maintainers :-D