[GH-ISSUE #82] Docker version tag for major/minor version branch #54

New issue

Closed

opened 2026-03-15 12:18:30 +03:00 by kerem · 3 comments

kerem commented

2026-03-15 12:18:30 +03:00

Owner

Originally created by @ocean90 on GitHub (Apr 3, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/82

Right now the Docker images are only available via the latest and the specific version tags. It would be helpful to be able to only define axllent/mailpit:v1.5 which would pull the latest version of the 1.5 branch. That would be 1.5.4 at the moment.

It seems like this only needs a change to github.com/axllent/mailpit@8e84b96233/.github/workflows/build-docker.yml (L34)

Maybe the docker/metadata-action action will be useful: https://github.com/docker/metadata-action#typesemver

Originally created by @ocean90 on GitHub (Apr 3, 2023). Original GitHub issue: https://github.com/axllent/mailpit/issues/82 Right now the Docker images are only available via the `latest` and the specific version tags. It would be helpful to be able to only define `axllent/mailpit:v1.5` which would pull the latest version of the `1.5` branch. That would be `1.5.4` at the moment. It seems like this only needs a change to https://github.com/axllent/mailpit/blob/8e84b96233ef7f60a11695557776be521c875319/.github/workflows/build-docker.yml#L34 Maybe the [docker/metadata-action](https://github.com/docker/metadata-action) action will be useful: https://github.com/docker/metadata-action#typesemver

kerem

2026-03-15 12:18:30 +03:00

closed this issue
added the
github_actions

docker
labels

kerem commented

2026-03-15 12:18:46 +03:00

Author

Owner

@axllent commented on GitHub (Apr 3, 2023):

Thanks for the suggestion, this is a good idea. I think that the docker/metadata-action is probably an overkill as it is designed to also push images (I just need to work out that the major.minor version is), so I'm going to try another simpler action first. Assuming this works (you never know until you try), the next release should include a mailpit:v1.5 tag 👍 I will leave this open until the next release (which are fairly regular).

@axllent commented on GitHub (Apr 3, 2023): Thanks for the suggestion, this is a good idea. I think that the docker/metadata-action is probably an overkill as it is designed to also push images (I just need to work out that the major.minor version is), so I'm going to try another simpler action first. Assuming this works (you never know until you try), the next release should include a `mailpit:v1.5` tag :+1: I will leave this open until the next release (which are fairly regular).

kerem commented

2026-03-15 12:18:51 +03:00

Author

Owner

@ocean90 commented on GitHub (Apr 3, 2023):

Sounds good! I don't think it will be push stuff as it only provides an output for the metadata which can be used by the push action. The readme has a good example for this.

@ocean90 commented on GitHub (Apr 3, 2023): Sounds good! I don't think it will be push stuff as it only provides an output for the metadata which can be used by the push action. The readme has a good example for this.

kerem commented

2026-03-15 12:18:56 +03:00

Author

Owner

@axllent commented on GitHub (Apr 4, 2023):

I've tested this on a separate testing repo and the action I am using to detect the major/minor version is working as expected. Given there are no current changes it may be a while before another release, so in the interim I have manually pushed a v1.5 tag (identical currently to v1.5.4) so you can start using that already if you like. When newer v1.5.* releases are created, the v1.5 tag will be updated, then v.16 will get added and updated etc when the release tags reach v1.6.* etc.

I'll close this ticket as it is effectively done now (just waiting for more releases). Thanks again for the suggestion.

@axllent commented on GitHub (Apr 4, 2023): I've tested this on a separate testing repo and the action I am using to detect the major/minor version is working as expected. Given there are no current changes it may be a while before another release, so in the interim I have manually pushed a v1.5 tag (identical currently to v1.5.4) so you can start using that already if you like. When newer v1.5.* releases are created, the v1.5 tag will be updated, then v.16 will get added and updated etc when the release tags reach v1.6.* etc. I'll close this ticket as it is effectively done now (just waiting for more releases). Thanks again for the suggestion.

kerem referenced this issue

2026-03-15 14:18:17 +03:00

[PR #54] [CLOSED] Bump golang.org/x/net from 0.5.0 to 0.7.0 #426