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

[GH-ISSUE #2068] [FEAT]: Improve versioning latest release in public S3 bucket #1345

New Issue
Closed
opened 2026-02-22 18:24:22 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:24:22 -05:00
Owner
Copy Link
Copy Source

Originally created by @ddaws on GitHub (Aug 8, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2068

What would you like to see?

It would be really helpful for packaging if the latest version of the app was also published to the legacy directory of the public S3 bucket used for distributing binaries and bundles.

Pacman packages built with makepkg verify checksums, but this is harder to do if the URL used to retrieve assets aren't versioned. This means the package can break if the files in latest are updated but the checksums in the package configuration aren't updated.

Here is an AUR package that could benefit from improved versioning
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=anythingllm-desktop-bin#n29

Originally created by @ddaws on GitHub (Aug 8, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2068 ### What would you like to see? It would be really helpful for packaging if the latest version of the app was also published to the `legacy` directory of the public S3 bucket used for distributing binaries and bundles. Pacman packages built with makepkg verify checksums, but this is harder to do if the URL used to retrieve assets aren't versioned. This means the package can break if the files in `latest` are updated but the checksums in the package configuration aren't updated. Here is an AUR package that could benefit from improved versioning https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=anythingllm-desktop-bin#n29
yindo added the enhancementfeature request labels 2026-02-22 18:24:22 -05:00
yindo closed this issue 2026-02-22 18:24:22 -05:00
yindo commented 2026-02-22 18:24:22 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Aug 8, 2024):

Okay, will do this when we publish. When we make a new version we will dupe the files to its legacy folder version as well. Right now we have just been using the legacy folder before a new version release, but we can make it part of the release process now.

@timothycarambat commented on GitHub (Aug 8, 2024): Okay, will do this when we publish. When we make a new version we will dupe the files to its legacy folder version as well. Right now we have just been using the legacy folder before a new version release, but we can make it part of the release process now.
yindo changed title from [FEAT]: Improve versioning latest release in public S3 bucket to [GH-ISSUE #2068] [FEAT]: Improve versioning latest release in public S3 bucket 2026-06-05 14:40:16 -04:00
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 enhancement feature request
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#1345
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?