John Oliver

To be clear here, I assume what you are asking is that we add support for this usecase in our api so that you can take advantage of it, but...

Calculating this page for an arbitrary set of user supplied filters would be potentially a comparatively expensive operation, and I am not sure if it offers a significant increase in...

The version is `21.0.2+13-LTS`, i.e: https://[api.adoptium.net/v3/assets/version/21.0.2+13-LTS](https://api.adoptium.net/v3/assets/version/21.0.2+13-LTS) easiest way to find the version is from: https://[api.adoptium.net/v3/info/release_versions?version=[21,22]&release_type=ga](https://api.adoptium.net/v3/info/release_versions?version=[21,22]&release_type=ga)

the version in the installer path: https://api.adoptium.net/v3/installer/version/jdk-21.0.1%2B12/windows/x64/jdk/hotspot/normal/eclipse?project=jdk is the release name/tag `jdk-21.0.1+12` and not the version: https://github.com/adoptium/temurin21-binaries/releases/tag/jdk-21.0.1%2B12 If anything this is actually a badly named path as it makes it...

I think the issue is you have given a url that actually exists, so should not 404, in fact will 302 you to the binary you requested, unfortunately what probably...

To some extent this is already supported as the upstream builds do sign their binaries, for instance if you look at: https://api.adoptopenjdk.net/v3/assets/version/%5B11%2C12%5D?vendor=openjdk You can see that binaries also have a...

This is expected behaviour, the two versions of the releases are: ``` "version_data": { "adopt_build_number": 1, "build": 12, "major": 21, "minor": 0, "openjdk_version": "21.0.1+12-LTS", "optional": "LTS", "security": 1, "semver": "21.0.1+12.1.LTS"...

should be there now

The issue is that the versions are: ``` "version_data": { "build": 12, "major": 21, "minor": 0, "openjdk_version": "21.0.1-beta+12-202312271138", "optional": "202312271138", "pre": "beta", "security": 1, "semver": "21.0.1-beta+12.0.202312271138" } ``` vs ```...

My learning with the mistake of using semver in the V3 API was dont try to fit a square peg in a round hole. Java uses its version scheme 322,...