swagger-api / swagger-api/swagger-ui
Major and minor version tags in Dockerhub
Open
Nobody has claimed this yet.
cat: docker
cat: packaging
type: enhancement
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Please publish images in Dockerhub with major (e.g. v3) and minor version (e.g. v3.20) tags so that users don't have to risk using the latest tag (Which may introduce breaking changes) or specific tags (e.g. v3.20.9 ) which do not receive updates.
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
The issue does not name files, tests, or a release entry point. Start by locating the Docker Hub publishing setup and how version tags are generated; done means published images receive major and minor tags such as v3 and v3.20 alongside specific version tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100