mirror of
https://github.com/open-webui/mcpo.git
synced 2026-11-05 01:27:39 +00:00
[GH-ISSUE #179] feat: proper versioning for docker images #79
Labels
No labels
bug
can't reproduce
documentation
enhancement
good first issue
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/mcpo#79
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @proud-nerd on GitHub (Jun 14, 2025).
Original GitHub issue: https://github.com/open-webui/mcpo/issues/179
Check Existing Issues
Problem Description
I like to tag my images to specific versions (preferably semver) and add them to my monitoring so I can read release notes before updating. There are release notes with proper versions for this project, but it feels unnecessary complicated to find out what docker image relates to which version.
Desired Solution you'd like
I'd like to have one docker image for each release, tagged with the corresponding version.
Alternatives Considered
It's possible to use the git commit-hash tags, but that's hard to keep track of when trying to figure out which release notes I need to read before updating
Additional Context
No response
@connelhooley commented on GitHub (Apr 2, 2026):
I'd like to second this request, there is sem-versioning in the github releases, currently the latest version is: v0.0.20
If we would have docker images tagged with this it would help a lot with those of us that use tools like renovate bot.