[Bug] Please follow the rules of SemVer!

[prokopsimek]

There are breaking changes between versions 1.0.8 and 1.1.0. Such as this: v1.0.8...v1.1.0#diff-26675fc047d31ed224b97b138f59e9eadb2b20b8656c5641899526fc7db8dc75

Could you follow the rules of Semver.org to avoid mistakes?

Thanks!

[dirkbrnd]

Hi @prokopsimek
We don't follow SemVer exactly, because it doesn't suit the pace of our project perfectly. We don't think it would be appropriate to do a major version bump for small but necessary breaking changes (sometimes related to 3rd parties that change).

If we introduce a breaking change, we will update the minor version, and reserve major versions for large reworks that changes a lot of the developer experience. Our product is still in relatively early stages of development, so breaking changes could happen, and we try and document this as best as possible.

I will make an effort to document our versioning strategy so it is more visible.

[prokopsimek]

Hi @dirkbrnd, thanks for the explanation. I now understand your versioning and can keep track of even minor releases. I’d also recommend clearly stating breaking changes in your releases to make it easier to identify what needs to be updated. I understand that you're still in the early stages of development, so maybe that can come later.

I must say that the learning curve of Phidata/Agno is the best compared to other agentic frameworks. Keep up the great work! I’d love to see improvements in versioning and the changelog to ensure I can upgrade my dependencies smoothly. :-)

[dirkbrnd]

@prokopsimek thanks for the feedback! I'll make it a separate heading in the changelog to ensure it is communicated correctly. I'll try and update it retrospectively as well.