Five releases in a month, two bugs that hit me — please give us a stable channel

[xiliangm]

First, a quick note: I don't write English, so this post was drafted with AI help. Sorry if anything reads stiff — the events and the frustration are all mine.

I use DeepTutor every day, and I genuinely like it. That's why I'm writing this.

Two weeks ago — the Partner bug (#1587). Five times in one day, the app injected a fake "the user asked to create a Partner" instruction into my normal chats. I never asked for a Partner. Your own contributor traced it in the issue: two word lists, no context check — and my own message tripped it, because "I want to file an issue about… Partner…" happens to contain one word from each list. It interrupted answers, killed conversations, and fired once while I was writing the bug report about it. Like calling the fire department to report a fire and getting sprayed because your call contained the word "fire".

This week — v1.6.12 (#1641). Here's the part that gets me: v1.6.12 is the release that carried those #1587 fixes — and the same release broke every .md upload. Every Markdown file I add to Immersive Reading now opens as one page: title, a few lines, done. Switching parsing engines does nothing. Files uploaded before the upgrade still read fine, so it's not my files. A contributor opened a fix (#1637); it's still unreviewed. I've filed #1641.

In between — the 1.5 → 1.6 redesign moved all my furniture. Maybe it's cleaner underneath. I still had to relearn the whole house.

One release fixes my last bug and ships my next one. That's not bad luck — that's what happens when five releases land in under a month (Sep 3, 6, 8, 24, 27) while, per your own #1222, the Python tests haven't actually run in CI for two releases, and your own v1.6.6 notes admit v1.6.5 had been "masking older breakage". Both bugs that hit me were silent — no error message, just wrong behavior that made me doubt my own files first.

The ask: separate "developing fast" from "releasing fast". Keep a beta channel at the current pace — daily is fine there. Make stable slower: monthly, or every six weeks. An LTS release that only receives bug fixes would be even better. And fix the CI gate first, because right now it's standing open.

Thank you for building this. It's the best learning tool I've used, and that's exactly why silent failures sting.