restrictive version check limits usability of modified images
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
With the current check of the image version format
it is impossible to run images with custom tags (e.g. those committed with a user-chosen version).
Users would like flexibility on versioning , e.g. to 5.0.5-updated-tex
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 reading lib/shared-functions.sh at line 13 and reproduce the version check with the example tag 5.0.5-updated-tex. Determine the validation behavior needed to permit user-chosen image tags while preserving the existing version handling. Done means modified images with custom tags can be used successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100