When v2.0.0?

[Ionys320]

⚠️ Please verify that your question has not already been reported

• I have searched the existing issues and found no similar reports.

🛡️ Security Policy

• I have read and agree to Uptime Kuma's Security Policy.

📝 Describe your problem

Hi!
I would like to know if there is any release date for v2, or what are the milestones that must be solved. Waiting for a looot of v2 features (some that I made), but can't switch to v2 easily using YunoHost until v2 is officially released.

📝 Error Message(s) or Log

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

Debian GNU/Linux 12

🌐 Browser

Vivaldi 7.4.3684.46 (Stable channel) (64 bits)

🖥️ Deployment Environment

• Runtime Environment:
  • YunoHost: Version 12.0.17
• Database:
  • SQLite: Embedded
• Database Storage:
  • Filesystem:
    • Linux: ext4
  • Storage Medium: SSD
• Uptime Kuma Setup:
  • Number of monitors: 57

[CommanderStorm]

From my pov nothing is blocking an immediate release.

Maybe the following would be nice to change before we roll out, given this could be breaking ^^:

• added option to force ipv4 or ipv6 for http(s) monitor type #5880 (comment)

[dorianborovina]

I was wondering too. :)

[CommanderStorm]

or what are the milestones that must be solved

@Ionys320 if you have some spare time:
There are a few MAJOR bugs from v2.0 which are bad ^^

• invalid time value after enacting an mainenance fucking with notifications, login, ... #5780
• Scheduled maintenance starts one minute later every day #5872
• (not really reproducible) Receiving a trace error: insert into 'stat_hourly' - Duplicate entry '43-1731949200' for key 'stat_hourly_monitor_id_timestamp_unique' #5357

[Ionys320]

Hi @CommanderStorm, made some PRs for the two first bugs. Will try to check the last one when I'll have more time!

Hoping 2.0.0-beta.4 will be the last Beta version of v2!

[TingTing1990]

or what are the milestones that must be solved

@Ionys320 if you have some spare time: There are a few MAJOR bugs from v2.0 which are bad ^^

• invalid time value after enacting an mainenance fucking with notifications, login, ... #5780
• Scheduled maintenance starts one minute later every day #5872
• (not really reproducible) Receiving a trace error: insert into 'stat_hourly' - Duplicate entry '43-1731949200' for key 'stat_hourly_monitor_id_timestamp_unique' #5357

I want to use uptime now and don't want to use V1 to avoid the hassle of upgrading to V2, can I just use ghcr.io/louislam/uptime-kuma:2.0.0-beta.3 for now and wait for the bug fixes until the official release?

[CommanderStorm]

can I just use ghcr.io/louislam/uptime-kuma:2.0.0-beta.3 for now

Yes

[edgicat]

can I just use ghcr.io/louislam/uptime-kuma:2.0.0-beta.3 for now

Yes

It might be worth letting people know are archived logs being migrated to v2 on initial startup. Perhaps something on the webpage until complete would be good too.

[CommanderStorm]

That migration takes a while and that people should do a backup is in the migration guide, or are we talking about different places in the docs?

[edgicat]

That migration takes a while and that people should do a backup is in the migration guide, or are we talking about different places in the docs?

Well that sounds like great advice, but unfortunately I didn't see any migration guide 🤦🏻.

I found I had a problem with my home assistant uptime Kuma HACS integration. When I checked my uptime Kuma dashboard it reported there was an update. I clicked on the date link and it took me straight to beta3 page on GitHub:
https://github.com/louislam/uptime-kuma/releases
A great page full of info on enhancements and fixes, but nothing on upgrading, that I could see.

I explored the home page on git hub:
https://github.com/louislam/uptime-kuma

Then followed the docker how to update link:
https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

My bad if I've missed a vital page, it took me a little while to check the docker logs to see it was migrating event log history. Once I realised I let it do it's thing. If I had seen something on the beta page perhaps at the very top or the GitHub home page ref migration to v2 I would have followed it. No biggy from my point of view, just thought it was worth noting hence my post here.

Keep up the good work