Merge pull request sameersbn#3273 from sachilles/upgrade-to-19.1.2

Upgrade GitLab CE to 19.1.2

Author: sachilles

Changelog.md

@@ -3,6 +3,15 @@
 This file only reflects the changes that are made in this image. Please refer to the upstream GitLab [CHANGELOG](https://
 gitlab.com/gitlab-org/gitlab-foss/blob/master/CHANGELOG.md) for the list of changes in GitLab.
 
+## 19.1.2
+
+- gitlab: upgrade CE to v19.1.2
+- gitaly: upgrade to v19.1.2
+- gitlab-pages: upgrade to v19.1.2
+- golang: upgrade to v1.26.4
+- rubygems: upgrade to v4.0.15
+- ubuntu: upgrade to noble-20260610
+
 ## 19.1.1
 
 - gitlab: upgrade CE to v19.1.1

Dockerfile

@@ -1,15 +1,15 @@
-FROM ubuntu:noble-20260509.1
+FROM ubuntu:noble-20260610
 
-ARG VERSION=19.1.1
+ARG VERSION=19.1.2
 
 ENV GITLAB_VERSION=${VERSION} \
     RUBY_VERSION=3.3.11 \
     RUBY_SOURCE_SHA256SUM="59f0fafb1a59a05dc3765117af3fa68e153eb48254708549f321c1e9e078d7a0" \
-    RUBYGEMS_VERSION=4.0.14 \
-    GOLANG_VERSION=1.26.4 \
+    RUBYGEMS_VERSION=4.0.15 \
+    GOLANG_VERSION=1.26.5 \
     GITLAB_SHELL_VERSION=14.54.0 \
-    GITLAB_PAGES_VERSION=19.1.1 \
-    GITALY_SERVER_VERSION=19.1.1 \
+    GITLAB_PAGES_VERSION=19.1.2 \
+    GITALY_SERVER_VERSION=19.1.2 \
     GITLAB_USER="git" \
     GITLAB_HOME="/home/git" \
     GITLAB_LOG_DIR="/var/log/gitlab" \

README.md

@@ -1,4 +1,4 @@
-# sameersbn/gitlab:19.1.1
+# sameersbn/gitlab:19.1.2
 
 [![CircleCI](https://circleci.com/gh/sameersbn/docker-gitlab/tree/master.svg?style=svg)](https://circleci.com/gh/sameersbn/docker-gitlab/tree/master)
 
@@ -129,7 +129,7 @@ Your docker host needs to have 1GB or more of available RAM to run GitLab. Pleas
 Automated builds of the image are available on [Dockerhub](https://hub.docker.com/r/sameersbn/gitlab) and is the recommended method of installation.
 
 ```bash
-docker pull sameersbn/gitlab:19.1.1
+docker pull sameersbn/gitlab:19.1.2
 ```
 
 You can also pull the `latest` tag which is built from the repository *HEAD*
@@ -211,7 +211,7 @@ docker run --name gitlab -d \
     --env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY=["long-and-random-alpha-numeric-string"]' \
     --env 'GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT=long-and-random-alpha-numeric-string' \
     --volume /srv/docker/gitlab/gitlab:/home/git/data \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 *Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `GITLAB_PORT` and other configuration options*
@@ -246,7 +246,7 @@ Volumes can be mounted in docker by specifying the `-v` option in the docker run
 ```bash
 docker run --name gitlab -d \
     --volume /srv/docker/gitlab/gitlab:/home/git/data \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 ### Database
@@ -309,7 +309,7 @@ docker run --name gitlab -d \
     --env 'DB_NAME=gitlabhq_production' \
     --env 'DB_USER=gitlab' --env 'DB_PASS=password' \
     --volume /srv/docker/gitlab/gitlab:/home/git/data \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 ##### Linking to PostgreSQL Container
@@ -353,7 +353,7 @@ We are now ready to start the GitLab application.
 ```bash
 docker run --name gitlab -d --link gitlab-postgresql:postgresql \
     --volume /srv/docker/gitlab/gitlab:/home/git/data \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 Here the image will also automatically fetch the `DB_NAME`, `DB_USER` and `DB_PASS` variables from the postgresql container as they are specified in the `docker run` command for the postgresql container. This is made possible using the magic of docker links and works with the following images:
@@ -391,7 +391,7 @@ The image can be configured to use an external redis server. The configuration s
 ```bash
 docker run --name gitlab -it --rm \
     --env 'REDIS_HOST=192.168.1.100' --env 'REDIS_PORT=6379' \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 #### Linking to Redis Container
@@ -418,7 +418,7 @@ We are now ready to start the GitLab application.
 
 ```bash
 docker run --name gitlab -d --link gitlab-redis:redisio \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 #### Mail
@@ -431,7 +431,7 @@ If you are using Gmail then all you need to do is:
 docker run --name gitlab -d \
     --env 'SMTP_USER=USER@gmail.com' --env 'SMTP_PASS=PASSWORD' \
     --volume /srv/docker/gitlab/gitlab:/home/git/data \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of SMTP parameters that can be specified.
@@ -471,7 +471,7 @@ docker run --name gitlab -d \
     --env 'IMAP_USER=USER@gmail.com' --env 'IMAP_PASS=PASSWORD' \
     --env 'GITLAB_INCOMING_EMAIL_ADDRESS=USER+%{key}@gmail.com' \
     --volume /srv/docker/gitlab/gitlab:/home/git/data \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of IMAP parameters that can be specified.
@@ -555,7 +555,7 @@ docker run --name gitlab -d \
     --env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_PORT=10443' \
     --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
     --volume /srv/docker/gitlab/gitlab:/home/git/data \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 In this configuration, any requests made over the plain http protocol will automatically be redirected to use the https protocol. However, this is not optimal when using a load balancer.
@@ -571,7 +571,7 @@ docker run --name gitlab -d \
  --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
  --env 'NGINX_HSTS_MAXAGE=2592000' \
  --volume /srv/docker/gitlab/gitlab:/home/git/data \
- sameersbn/gitlab:19.1.1
+ sameersbn/gitlab:19.1.2
 ```
 
 If you want to completely disable HSTS set `NGINX_HSTS_ENABLED` to `false`.
@@ -594,7 +594,7 @@ docker run --name gitlab -d \
     --env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_PORT=443' \
     --env 'GITLAB_HTTPS=true' --env 'SSL_SELF_SIGNED=true' \
     --volume /srv/docker/gitlab/gitlab:/home/git/data \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 Again, drop the `--env 'SSL_SELF_SIGNED=true'` option if you are using CA certified SSL certificates.
@@ -642,7 +642,7 @@ Let's assume we want to deploy our application to '/git'. GitLab needs to know t
 docker run --name gitlab -it --rm \
     --env 'GITLAB_RELATIVE_URL_ROOT=/git' \
     --volume /srv/docker/gitlab/gitlab:/home/git/data \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 GitLab will now be accessible at the `/git` path, e.g. `http://www.example.com/git`.
@@ -869,14 +869,14 @@ Also the container processes seem to be executed as the host's user/group `1000`
 ```bash
 docker run --name gitlab -it --rm [options] \
     --env "USERMAP_UID=$(id -u git)" --env "USERMAP_GID=$(id -g git)" \
-    sameersbn/gitlab:19.1.1
+    sameersbn/gitlab:19.1.2
 ```
 
 When changing this mapping, all files and directories in the mounted data volume `/home/git/data` have to be re-owned by the new ids. This can be achieved automatically using the following command:
 
 ```bash
 docker run --name gitlab -d [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:sanitize
+    sameersbn/gitlab:19.1.2 app:sanitize
 ```
 
 #### Piwik
@@ -2675,7 +2675,7 @@ Execute the rake task to create a backup.
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake gitlab:backup:create
+    sameersbn/gitlab:19.1.2 app:rake gitlab:backup:create
 ```
 
 A backup will be created in the backups folder of the [Data Store](#data-store). You can change the location of the backups using the `GITLAB_BACKUP_DIR` configuration parameter.
@@ -2710,14 +2710,14 @@ you need to prepare the database:
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake db:setup
+    sameersbn/gitlab:19.1.2 app:rake db:setup
 ```
 
 Execute the rake task to restore a backup. Make sure you run the container in interactive mode `-it`.
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake gitlab:backup:restore
+    sameersbn/gitlab:19.1.2 app:rake gitlab:backup:restore
 ```
 
 The list of all available backups will be displayed in reverse chronological order. Select the backup you want to restore and continue.
@@ -2726,7 +2726,7 @@ To avoid user interaction in the restore operation, specify the timestamp, date
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake gitlab:backup:restore BACKUP=1515629493_2020_12_06_13.0.6
+    sameersbn/gitlab:19.1.2 app:rake gitlab:backup:restore BACKUP=1515629493_2020_12_06_13.0.6
 ```
 
 When using `docker-compose` you may use the following command to execute the restore.
@@ -2775,7 +2775,7 @@ The `app:rake` command allows you to run gitlab rake tasks. To run a rake task s
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake gitlab:env:info
+    sameersbn/gitlab:19.1.2 app:rake gitlab:env:info
 ```
 
 You can also use `docker exec` to run rake tasks on running gitlab instance. For example,
@@ -2788,7 +2788,7 @@ Similarly, to import bare repositories into GitLab project instance
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake gitlab:import:repos
+    sameersbn/gitlab:19.1.2 app:rake gitlab:import:repos
 ```
 
 Or
@@ -2819,7 +2819,7 @@ Copy all the **bare** git repositories to the `repositories/` directory of the [
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake gitlab:import:repos
+    sameersbn/gitlab:19.1.2 app:rake gitlab:import:repos
 ```
 
 Watch the logs and your repositories should be available into your new gitlab container.
@@ -2856,7 +2856,7 @@ To upgrade to newer gitlab releases, simply follow this 4 step upgrade procedure
 - **Step 1**: Update the docker image.
 
 ```bash
-docker pull sameersbn/gitlab:19.1.1
+docker pull sameersbn/gitlab:19.1.2
 ```
 
 - **Step 2**: Stop and remove the currently running image
@@ -2886,7 +2886,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
 > **Note**: Since Gitlab 17.8 you need to provide `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY`,`GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY` and `GITLAB_SECRETS_ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT`. If not provided, these keys will be generated by gitlab. The image can be started without setting these parameters, **but you will lose the settings when you shutting down the container without taking a backup of `secrets.yml` and settings stored securely (such as the Dependency Proxy) will be unusable and unrecoverable.**
 
 ```bash
-docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:19.1.1
+docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:19.1.2
 ```
 
 ### Shell Access
@@ -2922,7 +2922,7 @@ You can also set your `docker-compose.yml` [healthcheck](https://docs.docker.com
 ```yml
 services:
   gitlab:
-    image: sameersbn/gitlab:19.1.1
+    image: sameersbn/gitlab:19.1.2
     healthcheck:
       test: ["CMD", "/usr/local/sbin/healthcheck"]
       interval: 1m

VERSION

@@ -1 +1 @@
-19.1.1
+19.1.2

contrib/docker-swarm/docker-compose.yml

@@ -20,7 +20,7 @@ services:
 
   gitlab:
     restart: always
-    image: sameersbn/gitlab:19.1.1
+    image: sameersbn/gitlab:19.1.2
     depends_on:
       - redis
       - postgresql

docker-compose.swarm.yml

@@ -62,7 +62,7 @@ services:
       - traefik-public
 
   gitlab:
-    image: sameersbn/gitlab:19.1.1
+    image: sameersbn/gitlab:19.1.2
     depends_on:
       - redis
       - postgresql

docker-compose.yml

@@ -21,7 +21,7 @@ services:
 
   gitlab:
     restart: always
-    image: sameersbn/gitlab:19.1.1
+    image: sameersbn/gitlab:19.1.2
     depends_on:
       - redis
       - postgresql

docs/container_registry.md

@@ -298,7 +298,7 @@ Execute the rake task with a removeable container.
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake gitlab:backup:create
+    sameersbn/gitlab:19.1.2 app:rake gitlab:backup:create
 ```
 
 ### Restoring Backups
@@ -315,7 +315,7 @@ Execute the rake task to restore a backup. Make sure you run the container in in
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake gitlab:backup:restore
+    sameersbn/gitlab:19.1.2 app:rake gitlab:backup:restore
 ```
 
 The list of all available backups will be displayed in reverse chronological order. Select the backup you want to restore and continue.
@@ -324,7 +324,7 @@ To avoid user interaction in the restore operation, specify the timestamp of the
 
 ```bash
 docker run --name gitlab -it --rm [OPTIONS] \
-    sameersbn/gitlab:19.1.1 app:rake gitlab:backup:restore BACKUP=1417624827
+    sameersbn/gitlab:19.1.2 app:rake gitlab:backup:restore BACKUP=1417624827
 ```
 
 ## Upgrading from an existing GitLab installation
@@ -334,7 +334,7 @@ If you want enable this feature for an existing instance of GitLab you need to d
 - **Step 1**: Update the docker image.
 
 ```bash
-docker pull sameersbn/gitlab:19.1.1
+docker pull sameersbn/gitlab:19.1.2
 ```
 
 - **Step 2**: Stop and remove the currently running image
@@ -388,7 +388,7 @@ docker run --name gitlab -d [PREVIOUS_OPTIONS] \
 --env 'GITLAB_REGISTRY_CERT_PATH=/certs/registry-auth.crt' \
 --env 'GITLAB_REGISTRY_KEY_PATH=/certs/registry-auth.key' \
 --link registry:registry
-sameersbn/gitlab:19.1.1
+sameersbn/gitlab:19.1.2
 ```
 
 [storage-config]: https://docs.docker.com/registry/configuration/#storage

docs/docker-compose-keycloak.yml

@@ -20,7 +20,7 @@ services:
 
   gitlab:
     restart: always
-    image: sameersbn/gitlab:19.1.1
+    image: sameersbn/gitlab:19.1.2
     depends_on:
       - redis
       - postgresql

docs/docker-compose-registry.yml

@@ -20,7 +20,7 @@ services:
 
   gitlab:
     restart: always
-    image: sameersbn/gitlab:19.1.1
+    image: sameersbn/gitlab:19.1.2
     volumes:
       - gitlab-data:/home/git/data:Z
       - gitlab-logs:/var/log/gitlab