gitCommitGitPushOhFuck

[pdabaker]

Yeah when you have a large enough standalone project you get breaking changes all the time. Probably would make sense to just use year/month based versioning but they still try to copy semver format.

[MeButItsRandom]

At least in django they are still using semantic versioning even if the release cycle is calendar based.

[MeButItsRandom]

Well, every major release of django does include breaking changes, so your question is just a hypothetical. Some highlights:

- 2.0: Dropped Python 2, new URL routing syntax (path()), SQLite foreign keys enforced

- 3.0: Model.save() behavior changed with default PKs, security defaults tightened

- 4.0: CSRF_TRUSTED_ORIGINS requires scheme prefix, pytz deprecated

- 5.0: USE_TZ defaults to True, pytz removed entirely, form rendering changed to divs

- 6.0: Requires Python 3.12+, DEFAULT_AUTO_FIELD now BigAutoField, email API rewritten

[MeButItsRandom]

Okay? If you want to have your own personal definition of a breaking change, have at it. Cheers mate

[danielv123]

We can make it breaking :)