spring-projects / spring-projects/spring-tools
use `latestPatch` from `generations` metadata for version validation (instead of `releases`)
Open
Nobody has claimed this yet.
for: claude
for: eclipse
for: vscode
theme: validation
type: enhancement
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
https://api.spring.io/projects/spring-boot/generations now contains information about the latest patch version, so we should use this for version validation instead of https://api.spring.io/projects/spring-boot/releases, which has information about the currently supported versions only.
Contributor guide
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.
Research direction
Start by locating the version-validation path that currently reads https://api.spring.io/projects/spring-boot/releases, then compare its expected data with the generations metadata endpoint. Done means validation uses latestPatch from generations and no longer relies on releases for the latest patch version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100