starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00

[GH-ISSUE #1645] v2.18 should be a beta release #1148

New issue

Closed

opened 2026-05-07 00:30:35 +02:00 by BreizhHardware · 5 comments

BreizhHardware commented

2026-05-07 00:30:35 +02:00

Owner

Originally created by @Fmstrat on GitHub (Mar 8, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1645

From the release:

The code was written by Cursor and Claude, but reviewed and heavily tested over 2-3 weeks by me. I created comparison documents, went through all queries multiple times and reviewed the logic over and over again. I also did load tests and manual regression tests, which took lots of evenings.

I'll not instantly switch ntfy.sh over. Instead, I'm kindly asking the community to test the Postgres support and report back to me if things are working (or not working). There is a one-off migration tool (entirely written by AI) that you can use to migrate.

It is poor practice to label something you do not trust as a formal release.

Originally created by @Fmstrat on GitHub (Mar 8, 2026). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1645 From the release: > The code was written by Cursor and Claude, but reviewed and heavily tested over 2-3 weeks by me. I created comparison documents, went through all queries multiple times and reviewed the logic over and over again. I also did load tests and manual regression tests, which took lots of evenings. > I'll not instantly switch ntfy.sh over. Instead, I'm kindly asking the community to test the Postgres support and report back to me if things are working (or not working). There is a one-off migration tool (entirely written by AI) that you can use to migrate. It is poor practice to label something you do not trust as a formal release.

BreizhHardware

2026-05-07 00:30:35 +02:00

closed this issue
added the
question
label

BreizhHardware commented

2026-05-07 00:30:36 +02:00

Author

Owner

@Fmstrat commented on GitHub (Mar 8, 2026):

Note: For me personally, with a full rewrite of code with AI, I will be looking for an alternative until ntfy is put through a security audit.

@Fmstrat commented on GitHub (Mar 8, 2026): Note: For me personally, with a full rewrite of code with AI, I will be looking for an alternative until ntfy is put through a security audit.

BreizhHardware commented

2026-05-07 00:30:36 +02:00

Author

Owner

@binwiederhier commented on GitHub (Mar 8, 2026):

I have reviewed and tested this for 2-3 weeks. It's not a rewrite. It's a re-org. I do concede that it maybe should have been labeled beta or released instantly.

So I'll release it to ntfy.sh tonight.

@binwiederhier commented on GitHub (Mar 8, 2026): I have reviewed and tested this for 2-3 weeks. It's not a rewrite. It's a re-org. I do concede that it maybe should have been labeled beta or released instantly. So I'll release it to ntfy.sh tonight.

BreizhHardware commented

2026-05-07 00:30:36 +02:00

Author

Owner

@binwiederhier commented on GitHub (Mar 8, 2026):

Note: For me personally, with a full rewrite of code with AI, I will be looking for an alternative until ntfy is put through a security audit.

What gave you the idea that this was a full rewrite? I moved things around with AI and added postgres support for the queries. Nobody has ever reviewed and tested anything more thoroughly than I did with this branch.

You are twisting what it actually is. You are assuming something that is not true.

If you have concrete questions I'm happy to answer

@binwiederhier commented on GitHub (Mar 8, 2026): > Note: For me personally, with a full rewrite of code with AI, I will be looking for an alternative until ntfy is put through a security audit. What gave you the idea that this was a full rewrite? I moved things around with AI and added postgres support for the queries. Nobody has ever reviewed and tested anything more thoroughly than I did with this branch. You are twisting what it actually is. You are assuming something that is not true. If you have concrete questions I'm happy to answer

BreizhHardware commented

2026-05-07 00:30:37 +02:00

Author

Owner

@binwiederhier commented on GitHub (Mar 8, 2026):

ntfy.sh was upgraded to 2.18.0. It works like a charm. 🥳

Please also feel free to review this document that outlines the differences between the 2.17.0/2.18.0 changes. I re-organized the structure of the packages (as I had to to support Postgres), so the GitHub diff is naturally very large. I used Claude and Cursor to create these comparison documents for me, which I used to review the code multiple times. I also actually did review the entire GitHub diff and did a manual and automated load test on a staging server, using the original load pattern on ntfy.sh.

If that is not enough to convince you then I don't know what will.

I should have labeled 2.18.0 a beta initially. That is correct. Everything else I stand by. My apologies if this has caused some folks to be upset, and for not labelling the release correctly.

Here is a selection of the comparison docs:

Full Package Comparison_ main vs postgres-support.pdf

comparison-2026-02-22.html

comparison-2026-03-01.html

@binwiederhier commented on GitHub (Mar 8, 2026): **ntfy.sh was upgraded to 2.18.0. It works like a charm.** 🥳 Please also feel free to review this document that outlines the differences between the 2.17.0/2.18.0 changes. I re-organized the structure of the packages (as I had to to support Postgres), so the GitHub diff is naturally very large. I used Claude and Cursor to create these comparison documents for me, which I used to review the code multiple times. I also actually did review the entire GitHub diff and did a manual and automated load test on a staging server, using the original load pattern on ntfy.sh. If that is not enough to convince you then I don't know what will. I should have labeled 2.18.0 a beta initially. That is correct. Everything else I stand by. My apologies if this has caused some folks to be upset, and for not labelling the release correctly. Here is a selection of the comparison docs: [Full Package Comparison_ main vs postgres-support.pdf](https://github.com/user-attachments/files/25826765/Full.Package.Comparison_.main.vs.postgres-support.pdf) [comparison-2026-02-22.html](https://github.com/user-attachments/files/25826786/comparison-2026-02-22.html) [comparison-2026-03-01.html](https://github.com/user-attachments/files/25826787/comparison-2026-03-01.html)

BreizhHardware commented

2026-05-07 00:30:37 +02:00

Author

Owner

@binwiederhier commented on GitHub (Mar 9, 2026):

Given that 2.18.0 is now officially released and a constructive conversation is not desired (there were some foul comments that GitHub auto-deleted I believe), I'll close this issue.

ntfy is and will forever be open source, and the free server is available to everyone. Please be kind to one another. The world has enough hate.

@binwiederhier commented on GitHub (Mar 9, 2026): Given that 2.18.0 is now officially released and a constructive conversation is not desired (there were some foul comments that GitHub auto-deleted I believe), I'll close this issue. ntfy is and will forever be open source, and the free server is available to everyone. Please be kind to one another. The world has enough hate.