[Release] Keep the 5.9 asset names in the stable release: latest/download links now 404

Open
#2,580 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
shell
Domain
release

Research direction

This is release-process work rather than a code fix: start by reading install.sh to see where TAG=v5.9.6 is pinned and how the script resolves the release it installs, then find the CI workflow that names the packaged artifacts (Hiddify-rpm-x64.rpm, Hiddify-Linux-x64.AppImage, and the arm64 variants) and compare it with what 5.5.5 published. Align the artifact names with the ones the docs link to and make the tag come from the release that served the script. Done means every latest/download/<file> link in the list resolves against the stable release and install.sh installs that same release rather than an older pinned tag.

Written by the indexing model from the issue text.

Description

The new docs (written for 5.9) link to https://github.com/hiddify/hiddify-app/releases/latest/download/<file>. The current stable "latest" is 5.5.5, so these return 404 today:

  • install.sh
  • Hiddify-rpm-x64.rpm, Hiddify-rpm-arm64.rpm
  • Hiddify-Linux-arm64.AppImage, Hiddify-Debian-arm64.deb
  • Hiddify-Linux-x64.AppImage (5.5.5 names it Hiddify-Linux-x64-AppImage.AppImage)

They exist in the 5.9.x pre-releases. Please keep exactly these names when 5.9 becomes the stable release, so the latest/download links work. (Same kind of breakage as #2273 and #2265.)

Note: install.sh pins TAG=v5.9.6 inside; when it is served from latest/download it should install the latest release (or the tag it came with), not an older one.

Dominant language
Dart
Stars
33.9k
Forks
3.2k
Avg merge
9h 34m
Merged PRs (30d)
22

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hiddify/hiddify-app

All issues in hiddify/hiddify-app

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.