[GH-ISSUE #489] version tag for latest version #94

New issue

Closed

opened 2026-03-03 12:08:14 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 12:08:14 +03:00

Owner

Originally created by @avihaybar on GitHub (Apr 27, 2021).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/489

Hi, great docker! we found it very useful.

However, one thing we didn't find on DockerHub is a version tag for the latest version.
(we prefer to pin down a version and not use the 'latest' tag).
is it possible create such a tag (the same way we could pull v1.21.2)

Originally created by @avihaybar on GitHub (Apr 27, 2021). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/489 Hi, great docker! we found it very useful. However, one thing we didn't find on DockerHub is a version tag for the latest version. (we prefer to pin down a version and not use the 'latest' tag). is it possible create such a tag (the same way we could pull v1.21.2)

kerem

2026-03-03 12:08:14 +03:00

closed this issue
added the
bug

docker
labels

kerem commented

2026-03-03 12:08:15 +03:00

Author

Owner

@fsouza commented on GitHub (Apr 27, 2021):

🤔 GitHub Actions should be doing that automatically. Will investigate what's going on and manually push.

@fsouza commented on GitHub (Apr 27, 2021): 🤔 GitHub Actions should be doing that automatically. Will investigate what's going on and manually push.

kerem commented

2026-03-03 12:08:15 +03:00

Author

Owner

@fsouza commented on GitHub (Apr 27, 2021):

Ok, I see what the issue is, we're doing a naked docker push and that no longer pushes all tags. Will fix the script and manually push the tags.

@fsouza commented on GitHub (Apr 27, 2021): Ok, I see what the issue is, we're doing a naked `docker push` and that no longer pushes all tags. Will fix the script and manually push the tags.

kerem commented

2026-03-03 12:08:15 +03:00

Author

Owner

@fsouza commented on GitHub (Apr 27, 2021):

This is now fixed. All tags are pushed and going forward GitHub Actions should do it for us properly.

If anyone is interested in auditing what I did, this is the script I used for each tag:

％ cat ~/regen-tag.bash
#!/usr/bin/env bash

set -euo pipefail

tag=${1}

git checkout "${tag}"
env GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build
env GITHUB_REF="refs/tags/${tag}" bash ci/docker-build.sh

And these are the tags I pushed:

％ cat ~/tags
v1.22.0
v1.22.1
v1.22.2
v1.22.3
v1.22.4
v1.22.5
v1.22.6
v1.22.7
v1.23.0
v1.23.1
v1.24.0

To run the script:

％ cat ~/tags | xargs -I @ ~/regen-tag.bash @

@fsouza commented on GitHub (Apr 27, 2021): This is now fixed. All tags are pushed and going forward GitHub Actions should do it for us properly. If anyone is interested in auditing what I did, this is the script I used for each tag: ``` ％ cat ~/regen-tag.bash #!/usr/bin/env bash set -euo pipefail tag=${1} git checkout "${tag}" env GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build env GITHUB_REF="refs/tags/${tag}" bash ci/docker-build.sh ``` And these are the tags I pushed: ``` ％ cat ~/tags v1.22.0 v1.22.1 v1.22.2 v1.22.3 v1.22.4 v1.22.5 v1.22.6 v1.22.7 v1.23.0 v1.23.1 v1.24.0 ``` To run the script: ``` ％ cat ~/tags | xargs -I @ ~/regen-tag.bash @ ```

kerem commented

2026-03-03 12:08:15 +03:00

Author

Owner

@avihaybar commented on GitHub (Apr 27, 2021):

Thanks!
Really appreciate it

@avihaybar commented on GitHub (Apr 27, 2021): Thanks! Really appreciate it

kerem referenced this issue

2026-03-03 12:29:31 +03:00

[PR #94] [MERGED] build(deps): bump @google-cloud/storage from 3.3.1 to 3.4.0 in /examples/node #332