[RfE] major_versions parameter "versions with all architectures"
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- api, backend-api-design
Research direction
Start with the /disco/v3.0/major_versions endpoint and its include_versions behavior, using the request and response examples in the issue as the baseline. Determine how a parameter for versions with all requested Temurin architectures should be defined and exposed, then verify that returned versions meet the all-platform-build requirement.
Written by the indexing model from the issue text.
Description
Hi,
currently when requesting all versions we get this:
Request:
curl "https://api.foojay.io/disco/v3.0/major_versions?ea=false&ga=true&maintained=true&include_build=false&include_versions=true" -H 'accept: application/json'
Response (excerpt):
{
"result": [
{
"major_version": 26,
"term_of_support": "STS",
"maintained": true,
"early_access_only": false,
"release_status": "ga",
"versions": [
"26"
]
},
{
"major_version": 25,
"term_of_support": "LTS",
"maintained": true,
"early_access_only": false,
"release_status": "ga",
"versions": [
"25.0.2.1",
"25.0.2",
"25.0.1",
"25"
]
},
{
"major_version": 21,
"term_of_support": "LTS",
"maintained": true,
"early_access_only": false,
"release_status": "ga",
"versions": [
"21.0.10.1",
"21.0.10",
"21.0.9",
"21.0.8",
"21.0.7",
"21.0.6",
"21.0.5",
"21.0.4",
"21.0.3",
"21.0.2",
"21.0.1",
"21"
]
}
],
"message": ""
}
However, I would like to only see the versions where all platform builds for temurin are available,
e.g. where I can download
- Temurin linux x64
- Temurin linux s390x
- Temurin AIX ppc64
- Temurin Mac aarch64
- Temurin Windows x64
etc.
Currently this is not easily possible without checking for every release.
- Dominant language
- Java
- Stars
- 154
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from foojayio/discoapi
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
Latest Corretto JDK 8 builds not returnedMay be free again @HanSolo claimed this 150 days ago, and no pull request is open. Openbug
All issues in foojayio/discoapi
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aoqia194/leaf-loader#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/streampark#4521 ·
-
Update license yearOpen0 - Backlog 1 - Ready documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
cbor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
FasterXML/jackson-dataformats-binary#844 ·
Maintainers usually reply within 1 day
-
Issue: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenAPITools/openapi-generator#25107 ·
Maintainers usually reply within 1 day