This allows the user to specify a release of specific version with a npm-flavor semver version constraint or a tag name. If a version constraint is provided, all releases' tag names are matched against that constraint, and the highest possible version is chosen.
API syntaxes:
/{user}/{repo}/{asset_regex} (implies latest stable release, backward compatible)
/{user}/{repo}@{semver|version_tag}/{asset_regex}
This resolves #1.
This allows the user to specify a release of specific version with a npm-flavor semver version constraint or a tag name. If a version constraint is provided, all releases' tag names are matched against that constraint, and the highest possible version is chosen.
API syntaxes:
/{user}/{repo}/{asset_regex}(implies latest stable release, backward compatible)/{user}/{repo}@{semver|version_tag}/{asset_regex}