It is a major version update. It contains some breaking changes. Please read the migration guide carefully if you want to upgrade from v1 to v2.
If your host is using Debian / Raspbian Buster, you should not upgrade. Due to a bug in the libseccomp2 library, it will run into a startup problem. Read more: https://github.com/louislam/uptime-kuma/issues/41#issuecomment-896164516
I read this, but it seems to be ARMv7 only, per the issue title. A little wary still, tho my docker host is x86. I guess I’ll try running a stand alone test to see if it boots.
Setting aside the funny (if you’re not affected) coincidence of AWS being down I have to say this is an exemplary way on how upgrades should be announced, executed and documented. There is a migration guide, but even if you don’t read it - in most cases the software will take care of it itself. Well done!
Only downside I see is how long it took for version 2.0 to get released. The previous stable release (1.23.16) was released almost one year ago.
I’ve been using this new version a few weeks now (since beta 3). The most significant advantage is the performance improvement. With 100+ monitors, the “old” version was very sluggish and took a long time to start.
Edit: I migrated my existing install to mariadb following this thread on github.
Sort of an ironic day to release an update for such a tool😆
@dear Mr bezos. Plz fix your shit. Sincerely. The uptime bear.
Why? I don’t think any part of uptimekuma relies on aws…
No but uptime tracking is relevant due to other services being down.
Ah, I see.
Thank you very much!
