Postgres 18 & Future?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
What's the intention for Postgres going forward?
So far we've relied on the bitnamilegacy images, but they didn't ship one for Postgres 18.
is there another provider we want to try building against?
Contributor guide
No contributing guide indexed for this repository
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 how the plugin currently relies on bitnamilegacy images and identify the configuration or entry points that determine the Postgres image provider and supported versions. Done means the project has a decided provider strategy for Postgres 18 and future versions, with the necessary support scope documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100