Prerelease matching

[Mosney]

https://glare.now.sh/vernesong/OpenClash/^luci-app-openclash.*\.ipk$
404

https://glare.now.sh/vernesong/OpenClash/luci-app-openclash_0.35.5-beta_all.ipk
{"github_api_msg":{"documentation_url":"https://developer.github.com/v3/repos/releases/#get-the-latest-release","message":"Not Found"},"message":"error from GitHub API"}

[Contextualist]

项目 vernesong/OpenClash 到目前为止没有任何的 stable releases，仅存在 prerelease。Glare 当前的 latest release 和 semver 的匹配原则是仅匹配 stable release。Prerelease 只能显式指定，如curl https://glare.now.sh/vernesong/[email protected]/^luci-app-openclash.*\.ipk$

或许可以考虑加入对 prerelease 的匹配，但我想考虑一下这样对当前匹配逻辑的整体影响和向后兼容性。欢迎谈谈你的想法。另参见 node-semver · prerelease-tags。

Repository vernesong/OpenClash does not have any stable releases but prereleases so far. Glare's current latest release and semver matching rules only concern stable releases. Prerelease can only be designated explicitly (e.g. curl https://glare.now.sh/vernesong/[email protected]/^luci-app-openclash.*\.ipk$)

We might support prerelease matching in the future, but that will potentially impact the vision of this project and backward compatibility. Any thoughts are welcome. See also node-semver · prerelease-tags.

[Mosney]

既然支持显式指定，是否可以用
https://glare.now.shxxx/yyy@all
https://glare.now.shxxx/yyy@release
https://glare.now.shxxx/yyy@prerelease
等类似的格式来更改匹配范围，默认保持匹配release，保障前向兼容性。