Dependabot does not cover npm, Docker or compose
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, docker-compose, typescript
- Domain
- build-system, devops
Research direction
Start by reading .github/dependabot.yml and checking the package manifests under clients/typescript, the Dockerfiles in src/FluentCMS.Host and templates/fluentcms, and the compose files that pin PostgreSQL and MinIO by digest. Add Dependabot entries for npm, Docker, and Docker Compose with the relevant directories. Done means Dependabot can propose npm package, Docker base image digest, and compose image updates.
Written by the indexing model from the issue text.
Description
Problem
.github/dependabot.yml covers github-actions and nuget only. The TypeScript client (clients/typescript), both Dockerfiles (src/FluentCMS.Host, templates/fluentcms) and both compose files (PostgreSQL and MinIO pinned by digest) never get update proposals, so security fixes to the documented deployable stack do not arrive.
Proposal
Add npm, docker and docker-compose entries for those directories.
Acceptance
- Dependabot proposes updates for the npm package, the base images and the compose images
Found in the code review of 17 Nov 2026 (S8).
Done together with #3312, which pins the Dockerfile base images by digest; the docker entry must then propose digest updates for them.
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:admin area:testing type:chore
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
approved area: ui bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day