Skip to content

Commit

Permalink
Upgrade to PostgreSQL 16.4
Browse files Browse the repository at this point in the history
Closes: #63
  • Loading branch information
ghusta committed Aug 11, 2024
1 parent 64d2447 commit 41602f0
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/docker-publish-on-tag.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ on:
env:
IMAGE_NAME: ghusta/postgres-world-db
ENABLE_QEMU: 1
POSTGRES_VERSION: 16.3
POSTGRES_VERSION: 16.4
BUILD_PUSH_ALPINE: 0

jobs:
Expand Down
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# Changelog

## 2.11.4 (2024-08-11)
Upgrade to PostgreSQL 16.4.
See https://www.postgresql.org/about/news/postgresql-164-158-1413-1316-1220-and-17-beta-3-released-2910/

## 2.11.3 (2024-05-10)
Upgrade to PostgreSQL 16.3.
See https://www.postgresql.org/about/news/postgresql-163-157-1412-1315-and-1219-released-2858/
Expand Down
2 changes: 1 addition & 1 deletion Dockerfile
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Init Example Database World on PostgreSQL
ARG POSTGRES_TAG=16.3
ARG POSTGRES_TAG=16.4
FROM postgres:$POSTGRES_TAG

ENV POSTGRES_USER world

Check warning on line 5 in Dockerfile

View workflow job for this annotation

GitHub Actions / build

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 5 in Dockerfile

View workflow job for this annotation

GitHub Actions / build

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 5 in Dockerfile

View workflow job for this annotation

GitHub Actions / build

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 5 in Dockerfile

View workflow job for this annotation

GitHub Actions / build

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 5 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker-publish

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Expand Down

0 comments on commit 41602f0

Please sign in to comment.