Jamesits / Jamesits/docker-postgres
Dependency Dashboard
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
View this repository on the Mend.io Web Portal.
Pending Status Checks
The following updates await pending status checks. To force their creation now, click on a checkbox below.
Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- Update dependency pgvector/pgvector to v0.8.6
- Update step-security/harden-runner action to v2.21.1
- Update actions/setup-node action to v7
- Click on this checkbox to rebase all open PRs at once
Detected Dependencies
docker-compose (1)
docker-compose.yml (1)
ghcr.io/ferretdb/ferretdb 2.7.0
dockerfile (1)
Dockerfile (2)
docker.io/library/postgres 18.4-trixie→ [Updates:18.6-trixie]docker.io/library/postgres 18.4-trixie→ [Updates:18.6-trixie]
github-actions (3)
.github/workflows/container-image-publish.yml (6)
step-security/harden-runner v2.20.0@bf7454d06d71f1098171f2acdf0cd4708d7b5920→ [Updates:v2.21.1]actions/checkout v7docker/setup-buildx-action v4docker/login-action v4docker/metadata-action v6docker/build-push-action v7.github/workflows/container-image-validation.yml (4)
step-security/harden-runner v2.20.0@bf7454d06d71f1098171f2acdf0cd4708d7b5920→ [Updates:v2.21.1]actions/checkout v7docker/setup-buildx-action v4docker/build-push-action v7.github/workflows/renovate-config-validation.yml (3)
step-security/harden-runner v2.20.0@bf7454d06d71f1098171f2acdf0cd4708d7b5920→ [Updates:v2.21.1]actions/checkout v7actions/setup-node v6→ [Updates:v7]
regex (1)
Dockerfile (2)
documentdb/documentdb v0.111pgvector/pgvector v0.8.5→ [Updates:v0.8.6]
renovate-config (1)
renovate.json
- Check this box to trigger a request for Renovate to run again on this repository
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 with the Dependency Dashboard, then review Dockerfile, docker-compose.yml, the three listed GitHub Actions workflows, and renovate.json. Check the existing pull requests before taking action; the work is done only when selected dependency updates pass the repository checks and the dashboard entries are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, github-actions, postgresql
- Domain
- ci-cd, databases, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100