spring-projects / spring-projects/spring-session
GitHub Releases changelists are broken/incorrect
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 55
Description
I was looking to see what version of Spring Session added JSpecify annotations, by looking at the github releases
I can see that by comparing 4.1.0 to 4.0.4, JSpecify was indeed added between these releases, but the 4.1.0 release notes do not mention it.
The release notes for 4.1.0-M1 include JSpecify, but that is marked as a pre-release. If I want to know what actually changed in 4.1.0, am I expected to also look at every milestone release?
Also for version bumps, the version numbers are misleading. For example, the actual change between for io.spring.nullability:io.spring.nullability.gradle.plugin between Spring Session 4.0.4 -> 4.1.0 was 0.10.0 -> 0.13.0.
Because that was bumped once in the milestone release, the 4.1.0 notes incorrectly claim the upgrade was from 0.0.11 to 0.0.13.
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 with the GitHub Releases entries for 4.1.0 and 4.1.0-M1, then inspect the 4.0.4...4.1.0 comparison linked in the issue. Determine how milestone changes and dependency version bumps are represented in the final release notes; done means the changelist includes the relevant JSpecify change and reports the actual version transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, java
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100