spring-projects / spring-projects/spring-security
CI should not publish SNAPSHOT artifacts to OSS after the last supported release
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
The existence of https://docs.spring.io/spring-security/site/docs/6.1.10-SNAPSHOT/api/ gives the impression that it may evolve into a release. However, since we are now out of the OSS support window for 6.1.x, there are no plans to release an OSS 6.1.10.
Perhaps the automation could consider whether or not such-and-such a version would be outside the support window and not publish accordingly.
This may be similar to https://github.com/spring-projects/spring-security/issues/13195
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
Review the automation that publishes the 6.1.x SNAPSHOT artifacts and compare its behavior with the related issue #13195. Verify how the support window is determined; done means an unsupported 6.1.x SNAPSHOT such as 6.1.10-SNAPSHOT is no longer published to OSS.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100