Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5761] [BUG]: Linux AppImage 1.13.0 reports version 1.12.1 in UI due to stale backend bundle #5559

New Issue
Closed
opened 2026-06-07 16:36:39 -04:00 by yindo · 1 comment
yindo commented 2026-06-07 16:36:39 -04:00
Owner
Copy Link
Copy Source

Originally created by @jarrodcolburn on GitHub (Jun 5, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5761

Describe the bug

The latest Linux AppImage for version 1.13.0 hosted on the CDN (https://cdn.anythingllm.com/latest/AnythingLLMDesktop.AppImage) incorrectly reports its version as 1.12.1 in the UI.

Despite the AppImage being the correct 1.13.0 build (matching the expected CDN file size), the bundled backend inside the AppImage still contains the hardcoded string "version":"1.12.1". Because the frontend queries /api/utils/metrics to get the version number, the UI displays 1.12.1 to the user, making them think the app has failed to update.

To Reproduce

  1. Download the latest Linux AppImage using the official script (curl -fsSL https://cdn.anythingllm.com/latest/installer.sh | sh)
  2. Open the AnythingLLM Desktop App.
  3. Observe the version number in the UI, which says 1.12.1 instead of 1.13.0.

Expected behavior

The UI should correctly display 1.13.0.

Technical Details

If you extract the AppImage (./AnythingLLMDesktop.AppImage --appimage-extract), you can observe the mismatch:

  • squashfs-root/resources/app.asar contains package.json with "version": "1.13.0"
  • However, the bundled backend code (e.g. squashfs-root/resources/backend/jobs/sync-watched-documents.js) has name:"anything-llm",version:"1.12.1" hardcoded in the minified bundle.

This suggests that during the Linux AppImage build process for 1.13.0, the backend was bundled (via combineModules.mjs) using a stale cache or before server/package.json was properly bumped to 1.13.0.

Originally created by @jarrodcolburn on GitHub (Jun 5, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5761 ### Describe the bug The latest Linux AppImage for version 1.13.0 hosted on the CDN (`https://cdn.anythingllm.com/latest/AnythingLLMDesktop.AppImage`) incorrectly reports its version as `1.12.1` in the UI. Despite the AppImage being the correct 1.13.0 build (matching the expected CDN file size), the bundled backend inside the AppImage still contains the hardcoded string `"version":"1.12.1"`. Because the frontend queries `/api/utils/metrics` to get the version number, the UI displays `1.12.1` to the user, making them think the app has failed to update. ### To Reproduce 1. Download the latest Linux AppImage using the official script (`curl -fsSL https://cdn.anythingllm.com/latest/installer.sh | sh`) 2. Open the AnythingLLM Desktop App. 3. Observe the version number in the UI, which says `1.12.1` instead of `1.13.0`. ### Expected behavior The UI should correctly display `1.13.0`. ### Technical Details If you extract the AppImage (`./AnythingLLMDesktop.AppImage --appimage-extract`), you can observe the mismatch: - `squashfs-root/resources/app.asar` contains `package.json` with `"version": "1.13.0"` - However, the bundled backend code (e.g. `squashfs-root/resources/backend/jobs/sync-watched-documents.js`) has `name:"anything-llm",version:"1.12.1"` hardcoded in the minified bundle. This suggests that during the Linux AppImage build process for 1.13.0, the backend was bundled (via `combineModules.mjs`) using a stale cache or before `server/package.json` was properly bumped to 1.13.0.
yindo closed this issue 2026-06-07 16:36:39 -04:00
yindo commented 2026-06-07 16:36:40 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 6, 2026):

This suggests that during the Linux AppImage build process for 1.13.0, the backend was bundled (via combineModules.mjs) using a stale cache or before server/package.json was properly bumped to 1.13.0.

This is more of a red herring. When we do the release the code is actually synced to the commits in this repo. Then we build desktop and then we do the version bump commit in this repo before making a GH release.

This is because of how we also have to make ports for the pg and render images and cannot do it all in one commit. The app.asar is the correct version regardless of what desktop says in other nested package.jsons.

If the UI says that version is x.y.z - that is the case in terms of feature parity

<!-- gh-comment-id:4640187551 --> @timothycarambat commented on GitHub (Jun 6, 2026): > This suggests that during the Linux AppImage build process for 1.13.0, the backend was bundled (via combineModules.mjs) using a stale cache or before server/package.json was properly bumped to 1.13.0. This is more of a red herring. When we do the release the code is actually synced to the commits in this repo. Then we build desktop and **then** we do the version bump commit in this repo before making a GH release. This is because of how we also have to make ports for the `pg` and `render` images and cannot do it all in one commit. The app.asar is the correct version regardless of what desktop says in other nested package.jsons. If the UI says that version is x.y.z - that is the case in terms of feature parity
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5559
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?