github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-21 09:21:15 -05:00
Code Issues 856 Packages Projects Releases 74 Wiki Activity

[GH-ISSUE #1049] Feature Request: Semantic versioning tags for docker images #1735

New Issue
Closed
opened 2026-04-16 08:31:10 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-16 08:31:10 -05:00
Owner
Copy Link

Originally created by @binzhou on GitHub (Jul 11, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1049

Originally assigned to: @oschwartz10612 on GitHub.

The official docker images at the moment are tagged with either the exact version (eg. "1.2.3") or "latest".

Could images be pushed and tagged with inexact version strings as well (eg. when pushing "1.2.3", also tag with "1.2" and "1")?

Assuming semantic versioning is used, that would allow folks more flexibility to make finer-grained trade-offs between the latest and greatest vs. stability. For example, I would like to make sure I'm picking up fixes while pinned to a specific feature set (ie. "1.2" in the above example).

It would be great to have this across all fosrl images (pangolin, gerbil, newt).

Originally created by @binzhou on GitHub (Jul 11, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1049 Originally assigned to: @oschwartz10612 on GitHub. The official docker images at the moment are tagged with either the exact version (eg. "1.2.3") or "latest". Could images be pushed and tagged with inexact version strings as well (eg. when pushing "1.2.3", also tag with "1.2" and "1")? Assuming semantic versioning is used, that would allow folks more flexibility to make finer-grained trade-offs between the latest and greatest vs. stability. For example, I would like to make sure I'm picking up fixes while pinned to a specific feature set (ie. "1.2" in the above example). It would be great to have this across all fosrl images (pangolin, gerbil, newt).
GiteaMirror added the enhancement label 2026-04-16 08:31:10 -05:00
GiteaMirror commented 2026-04-16 08:31:14 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Jul 11, 2025):

Yeah this is a good idea. Will do.

<!-- gh-comment-id:3063229196 --> @oschwartz10612 commented on GitHub (Jul 11, 2025): Yeah this is a good idea. Will do.
GiteaMirror commented 2026-04-16 08:31:15 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Sep 27, 2025):

Thanks, converting this to a discussion thread so others can upvote and participate!

<!-- gh-comment-id:3342084765 --> @miloschwartz commented on GitHub (Sep 27, 2025): Thanks, converting this to a discussion thread so others can upvote and participate!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1735
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?