sameersbn / sameersbn/docker-gitlab
PostgreSQL 16 needed for GitLab 18
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
The blog post on the release of GitLab 17.11 contains this bit:
In GitLab 18.0, the minimum-supported version of PostgreSQL will be version 16. To prepare for this change, on instances that don’t use PostgreSQL Cluster, upgrades to GitLab 17.11 will attempt to automatically upgrade PostgreSQL to version 16.
What are the prospects for a sameersbn/postgresql image with version 16?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the cited GitLab 17.11 release note and the current sameersbn/postgresql image configuration. The issue names no repository files or tests; done would require a PostgreSQL 16 image that supports the GitLab 18 requirement and is documented or published for users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100