Where is the TiddlyDesktop AppImage referred to in the ReadMe.md!?

[nman-in]

In the ReadMe.md the availability of an AppImage for installing TiddlyDesktop is made prominently with even a helpful link to the releases section of this GitHub account.

However, there's no appimage available there -- not for the latest version nor for the last few previous versions.

Please correct this mismatch because it's screwing with searches as well as AI. Either remove the mention of appimage from the readme, OR ensure that an appimage is compiled and available under releases.

Thank you.

[Jermolene]

Thanks @nman-in. The AppImage build was added in #309 by @emmanuelrosa. The CI script was last run in November 2025, and ran without errors. @emmanuelrosa do you see anything wrong?

[emmanuelrosa]

OK. Let's start from the beginning. You, @nman-in have absolutely no right to make these demands. We are not, nor will ever be your servants, nor the servants of search engines and LLMs. I suggest you adjust your approach accordingly, or expect to be rightfully ignored.

As for the cause of the issue, the latest release of TiddlyDesktop was in March of 2024. Following that, CI was added, and following that the AppImage build process was added. When the CI runs it builds the AppImage along with the archives, but the files are only staged for a short period of time; Long enough to obtain them and then include them in a new release. Importantly, the staging area is only accessible to the repo's owner.

In addition to the above, the TiddlyDesktop Git repo has the master branch as the default branch, and the master branch also serves as the development branch. In other words, there is no "stable/release" branch that can be used as the default branch and be indexed by search engines.

I know this creates a confusing situation, I've encountered this in other projects, but it's actually pretty normal. But even if it wasn't normal it wouldn't matter because the owner can manage the repo however he pleases without a care in the world. He's under no obligation to make your wishes come true, remember.

As mentioned in #309, here's a copy of the AppImage built by the CI at the time: https://drive.proton.me/urls/C5K8MMTJPG#LVklXvI2G9ri

Keep in mind that it's not really version 0.0.21, but rather a build off the master branch at that point in time. Not much has changed since, so it should be OK that the AppImage is a bit old.

Alternatively, you can fork this repo in GitHub, and then push a dummy commit to the master branch. That will trigger the CI and produce an AppImage, which you can then access.

[Jermolene]

Thank you @emmanuelrosa and apologies, there is evidently more to this than I had understood.

I'd be happy to adopt a stable/release branch architecture but as you note TiddlyDesktop has been somewhat dormant recently thanks to my workload. I still use it almost every day, though, and would like to keep the project ticking over.

I updated the readme (see c97c385), but presumably I should take this opportunity to make a new release? Will that automatically include the AppImage?

[emmanuelrosa]

Based on my understanding of the CI notes in the README, yes the AppImage should be included automatically. It should also include the other archives.

Since you just pushed a commit, the CI should trigger soon, if it hasn't already. But I don't think those files will be included in the release automatically until you push the git tag (ex. v0.0.21). Then when you create the relase using that tag, I believe that's when the build outputs are added automatically. It's something like that.