chore(deps): bump dockerode from 4.0.9 to 5.0.0 in /queueConsumer

[dependabot]

Bumps dockerode from 4.0.9 to 5.0.0.

Release notes

Sourced from dockerode's releases.

v5.0.0

What's Changed

• Bump picomatch from 2.3.1 to 2.3.2 by @​dependabot[bot] in apocas/dockerode#826
• Bump protobufjs from 7.3.2 to 7.5.5 by @​dependabot[bot] in apocas/dockerode#828
• Dropped uuid package, bumped minimum node version requirement.

Full Changelog: apocas/dockerode@v4.0.10...v5.0.0

v4.0.10

What's Changed

• Bump js-yaml from 4.1.0 to 4.1.1 by @​dependabot[bot] in apocas/dockerode#820
• fix(readme): update docker api links by @​parishahla in apocas/dockerode#823
• buildkit proto followProgress support by @​davidgamero in apocas/dockerode#824
• Bump minimatch from 5.1.6 to 5.1.9 by @​dependabot[bot] in apocas/dockerode#825

New Contributors

• @​parishahla made their first contribution in apocas/dockerode#823
• @​davidgamero made their first contribution in apocas/dockerode#824

Full Changelog: apocas/dockerode@v4.0.9...v4.0.10

Commits

• d8968eb chore: update chai to version 4.5.0 in package.json and package-lock.json
• 62ded54 fix: downgrade chai to 6.2.0 and mocha to 11.7.0
• 3f6f9c4 Update devDependencies: Upgrade chai to 6.2.2 and mocha to 11.7.5
• c37ff26 Merge pull request #828 from apocas/dependabot/npm_and_yarn/protobufjs-7.5.5
• 0f1a049 Bump protobufjs from 7.3.2 to 7.5.5
• c073e27 fix: update version to 5.0.0 and remove uuid dependency
• 8c4b4cd fix: update version to 4.0.12 and downgrade uuid dependency to 10.0.0
• 7e6f694 fix: update version to 4.0.12 and downgrade uuid dependency to 10.0.0
• 8124962 fix: update version to 4.0.11 and bump uuid dependency to 14.0.0
• 7118249 Merge pull request #826 from apocas/dependabot/npm_and_yarn/picomatch-2.3.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[greptile-apps]

Greptile Summary

This is a Dependabot-generated PR that upgrades dockerode from 4.0.9 to 5.0.0 in the queueConsumer service. The v5 release drops the internal uuid dependency and raises the minimum Node.js requirement to >=14.17, neither of which affects this codebase (it already targets a much newer Node.js runtime).

• The dockerode runtime version is bumped to ^5.0.0 and all public API usage in the service (container creation, log streaming, modem.demuxStream, ping, image inspection) is unaffected by the v5 changes.
• @types/dockerode in devDependencies remains at ^4.0.1, creating a minor version mismatch between the installed runtime and its TypeScript type definitions; this should be verified or updated.

Confidence Score: 4/5

Safe to merge; the only Docker API usage (container create, start, stop, log streaming, modem.demuxStream) is unchanged in v5.

Dockerode v5 removes only the internal uuid dependency and raises the minimum Node.js floor — neither affects this service. All existing dockerode call sites remain API-compatible. The one thing to double-check is whether @types/dockerode ^4.0.1 still compiles cleanly against the new runtime.

queueConsumer/package.json — verify or update @types/dockerode to match the new runtime major version.

Important Files Changed

Filename	Overview
queueConsumer/package.json	Bumps dockerode runtime from ^4.0.9 to ^5.0.0; the companion @types/dockerode dev-dependency remains at ^4.0.1, creating a version mismatch between the runtime and its type definitions.

Sequence Diagram

sequenceDiagram
    participant QC as queueConsumer
    participant pkg as package.json
    participant dockerode as dockerode (runtime)
    participant types as @types/dockerode (types)

    QC->>pkg: declare dependency
    pkg->>dockerode: ^5.0.0 (bumped from ^4.0.9)
    pkg->>types: ^4.0.1 (unchanged — version mismatch)
    dockerode-->>QC: "runtime API (uuid dropped, Node >=14.17)"
    types-->>QC: TypeScript types (still v4 signatures)

Loading

Comments Outside Diff (1)

1. queueConsumer/package.json, line 78 (link)

   The runtime package is now dockerode ^5.0.0, but @types/dockerode is still pinned to ^4.0.1. DefinitelyTyped type packages are expected to track the major version of the library they describe, so a major-version skew means the TypeScript compiler is checking your code against 4.x type signatures while the installed runtime is 5.x. Dockerode 5's only notable API change is dropping the internal uuid dependency (the public Docker Remote API surface is unchanged), so type errors are unlikely in practice — but if any 5.x type-level behaviour diverges, they would be silently missed. Bumping @types/dockerode to ^5.0.0 (if a matching release exists) or confirming the current types still compile cleanly would remove the ambiguity.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: queueConsumer/package.json
   Line: 78
   
   Comment:
   The runtime package is now `dockerode` `^5.0.0`, but `@types/dockerode` is still pinned to `^4.0.1`. DefinitelyTyped type packages are expected to track the major version of the library they describe, so a major-version skew means the TypeScript compiler is checking your code against 4.x type signatures while the installed runtime is 5.x. Dockerode 5's only notable API change is dropping the internal `uuid` dependency (the public Docker Remote API surface is unchanged), so type errors are unlikely in practice — but if any 5.x type-level behaviour diverges, they would be silently missed. Bumping `@types/dockerode` to `^5.0.0` (if a matching release exists) or confirming the current types still compile cleanly would remove the ambiguity.
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
queueConsumer/package.json:78
The runtime package is now `dockerode` `^5.0.0`, but `@types/dockerode` is still pinned to `^4.0.1`. DefinitelyTyped type packages are expected to track the major version of the library they describe, so a major-version skew means the TypeScript compiler is checking your code against 4.x type signatures while the installed runtime is 5.x. Dockerode 5's only notable API change is dropping the internal `uuid` dependency (the public Docker Remote API surface is unchanged), so type errors are unlikely in practice — but if any 5.x type-level behaviour diverges, they would be silently missed. Bumping `@types/dockerode` to `^5.0.0` (if a matching release exists) or confirming the current types still compile cleanly would remove the ambiguity.

```suggestion
        "@types/dockerode": "^5.0.0",
```

_{Reviews (1): Last reviewed commit: "chore(deps): bump dockerode from 4.0.9 t..." | Re-trigger Greptile}