It has been a while (two and a half years ago) since a new major release has been published. For multiple reasons, introducing breaking changes is bad, but for a package like Qowaiv it is even worse than for most packages: once you start using them, you’ll end up having the dependency everywhere. (Which is a good thing, I would argue.)
| Version | Downloads | Released | life time |
|---|---|---|---|
| 7.0.0 | t.b.d. | 2024-06-28 | t.b.d. |
| 6.0.0 | 57,738 | 2021-12-30 | 2y, 6m, 29d |
| 5.0.0 | 2,225 | 2019-12-11 | 2y, 0m, 19d |
| 4.0.0 | 4,969 | 2019-07-09 | 5m, 2d |
| 3.0.0 | 1,640 | 2016-11-30 | 2y, 8m, 9d |
| 2.0.0 | 2,926 | 2015-11-30 | 1y, 0m, 0d |
| 1.0.0 | 2,367 | 2015-10-13 | 1m, 27d |
Because of this, also for this release, breaking changes are kept to a minimum, and grouped together, although the last makes that releasing new majors still can become challenging.
So, most most breaking changes is about code being dropped, becuase is has been considdered a bad practice and due to that, being marked as obsolete for a long time.
In Clock there has been one change that gave me some headache, but I decided
to go forward with after all: Qowaiv.Now() returns a DateTimeOffset instead
of a DateTime, Clock.NowWithOffset has been dropped. In practice, you can
not longer get a DateTime back describing the local time as DateTime. Using
Clock.Now() was something I never liked due it’s ambigous nature. By returning
a DateTimeOffset that has been fixed.
The full list of changes:
I hope migrating to Qowaiv v7.0.0. will turn out to be a walk in the park, but if not, please let me know. I might be able to help you out.