Query Regarding the `latest` Tag
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 84
- Forks
- 38
- Avg merge
- 8h 13m
- Merged PRs (30d)
- 2
Description
I appreciate your daily maintenance efforts.
I noticed that the latest tag currently points to the same version as 3.2.2-jammy. However, I was expecting it to point to 3.3.0-jammy. Is this intentional?
If so, could you please clarify the policy regarding the latest tag?
If this is not intentional, could you kindly correct the version that the latest tag points to?
Refs
- https://hub.docker.com/layers/rubylang/ruby/latest/images/sha256-fd3727a60b6ecf9f28580ac0d42aa2a6b658ea66318009524fcc6445e5909cd5?context=explore
- https://hub.docker.com/layers/rubylang/ruby/3.2.2-jammy/images/sha256-fd3727a60b6ecf9f28580ac0d42aa2a6b658ea66318009524fcc6445e5909cd5?context=explore
- https://github.com/ruby/ruby-docker-images/pkgs/container/ruby/82149985?tag=latest
Contributor guide
No contributing guide indexed for this repository
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 comparing the Docker Hub references for latest and 3.2.2-jammy with the GitHub Packages entry linked in the issue, then check how the repository publishes and assigns image tags. Done means confirming whether latest should point to 3.3.0-jammy and either correcting the tag or documenting the applicable policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ruby
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100