github/vim-ale
1
0
Fork 0
mirror of https://github.com/webinstall/webi-installers.git synced 2026-04-06 18:36:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update answers with three-strategy fix details

Browse Source
This commit is contained in:
AJ ONeal
2026-03-11 11:42:59 -06:00
parent 0ae4d01d75
commit bbcaa0f464
1 changed files with 12 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
ANSWERS.md
View File

@@ -53,13 +53,19 @@ source-only GitHub releases get tarball + zipball + git entries.
entry. The resolver's version-descending + platform-first-then-any order means
git assets for old versions are never selected when newer binaries exist.
**No fix needed** in the Go resolver or classifier. The behavior is correct.
**Update (FIXED)**: The Go classifier now has three distinct strategies:
**Update**: Confirmed that regenerating the cache alone does NOT fix the Node.js
resolver. With the old ANYOS-first enumeration, jq and caddy still resolve to
`.git`, and rg still gets v0.1.6. The fix is in the Node.js resolver's triplet
enumeration order — specific OS must come before ANYOS, and versions must iterate
newest-first. The cache data is correct; the resolution logic was wrong.
1. **`github`** (`github_repo =`) — binary assets only. Releases with no
uploaded assets are skipped entirely. No more `.git`/tarball/zipball entries
for caddy, jq, shellcheck, etc.
2. **`githubsource`** (`github_source =`) — source tarball + zipball from
GitHub releases API. For packages installed from source (shell scripts).
aliasman, duckdns.sh, serviceman now use this.
3. **`gittag`** (`git_url =`) — git clone + tag enumeration (unchanged).
The Node.js resolver fix (specific OS before ANYOS, versions newest-first)
is still needed on your side. But the Go cache no longer produces the
problematic ANYOS entries for binary packages.
## Re: Issue 4 — darwin-universal (Hugo)