I will try my best to offer an explanation of why these changes were required, how we plan to slow down, not introduce such breaking changes anymore, and some history. I used to be the only …

Oct 14, 2024 · Hera supports 3.13 for the core features, but cicd (make test specifically) is blocked by the tests for new decorators breaking - varname seems to have a compatibility …

Sep 5, 2024 · Even allowing mixing the two syntaxes with the newer decorator feature flag as done in the PR will likely result in user code being stuck between the two syntaxes and then us …

Maybe it's time to remove that from Hera and, since it's a breaking change, it will be released under version 3.0.0. I will mark this as an enhancement! 👍 1 kitagry reacted with thumbs up …

- if you introduce a breaking change (removing arguments, removing objects, restructuring code such that it affects imports, etc.), increment the MAJOR version The general format is: ``` # …

Jan 9, 2022 · Removing v1 (and the concept of internal library versioning) introduces a breaking change in which we can safely deploy the necessary SSL verification changes you requested.

Mar 30, 2023 · I will try my best to offer an explanation of why these changes were required, how we plan to slow down, not introduce such breaking changes anymore, and some history. I …

So you can decide before merging how to bump - especially also because with a major version bump we expect breaking changes so you'd want to use it carefully, possibly restricting who …

if you introduce a breaking change (removing arguments, removing objects, restructuring code such that it affects imports, etc.), increment the MAJOR version The general format is:

I'm not 100% on-board on my own suggestion myself, as I think there are some collisions with pre-existing concepts which will probably lead to breaking changes.