Add updater container support for conda, deno, and nix#1681
Merged
Conversation
Copilot
AI
changed the title
[WIP] Add updater container support for conda, deno, and nix
Add updater container support for conda, deno, and nix
May 7, 2026
kbukum1
approved these changes
May 7, 2026
AbhishekBhaskar
approved these changes
May 7, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds missing updater container wiring for the conda, deno, and nix Dependabot ecosystems so jobs targeting those ecosystems can resolve a pinned updater image (via docker/containers.json) at runtime.
Changes:
- Added new
docker/Dockerfile.{conda,deno,nix}files that pin the upstreamghcr.io/dependabot/dependabot-updater-<ecosystem>images by tag + sha256 digest. - Registered
conda,deno, andnixinsrc/update-containers.tsso the manifest generator includes them. - Regenerated
docker/containers.jsonand rebuilt the bundleddist/artifacts to include the updated manifest.
Show a summary per file
| File | Description |
|---|---|
| src/update-containers.ts | Adds conda, deno, nix entries to the manifest used to generate docker/containers.json. |
| docker/Dockerfile.conda | Pins the upstream conda updater image (tag + digest). |
| docker/Dockerfile.deno | Pins the upstream deno updater image (tag + digest). |
| docker/Dockerfile.nix | Pins the upstream nix updater image (tag + digest). |
| docker/containers.json | Regenerated container manifest including the three new ecosystems. |
| dist/main/index.js | Rebuilt bundle so runtime code ships the updated container manifest. |
| dist/cleanup/index.js | Rebuilt bundle so runtime code ships the updated container manifest. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 5/7 changed files
- Comments generated: 0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three ecosystems shipped by
dependabot-core(conda,deno,nix) had no corresponding updater image wiring in this action, causing jobs targeting them to fail image resolution.Changes
docker/Dockerfile.{conda,deno,nix}— new single-FROMDockerfiles pinning the latest available versioned tag (v2.0.20260507203823) +sha256digest for each upstreamghcr.io/dependabot/dependabot-updater-<ecosystem>image (tag familyv2.0.20260427215009used by other ecosystems doesn't exist for these three yet)src/update-containers.ts— registers the three new keys in themanifestobject:docker/containers.json— regenerated vianpm run update-container-manifestdist/— rebuilt vianpm run packageOriginal prompt
Summary
Add updater container support for three ecosystems that are present in
dependabot/dependabot-corebut missing from this action:conda,deno, andnix.Why
dependabot-coreregisters these ecosystems (see the canonicalrequire "dependabot/<ecosystem>"list in core), and updater images are published toghcr.io/dependabot/dependabot-updater-<ecosystem>. However, this repository does not yet wire them up, so jobs targeting these ecosystems fail to resolve an image.Currently registered ecosystems live in:
src/update-containers.ts— themanifestmapdocker/— oneDockerfile.<ecosystem>per updaterdocker/containers.json— generated manifestAfter diffing against the full
dependabot-coreecosystem list, the missing ones are:conda,deno,nix.What to change
Create three new Dockerfiles under
docker/, each containing a singleFROMline pointing at the matching upstream updater image. Follow the exact pattern used by the existing files (e.g.docker/Dockerfile.bun,docker/Dockerfile.bazel):docker/Dockerfile.conda→FROM ghcr.io/dependabot/dependabot-updater-conda:<latest tag>@sha256:<digest>docker/Dockerfile.deno→FROM ghcr.io/dependabot/dependabot-updater-deno:<latest tag>@sha256:<digest>docker/Dockerfile.nix→FROM ghcr.io/dependabot/dependabot-updater-nix:<latest tag>@sha256:<digest>Use the same tag/digest version family as the other Dockerfiles already in the repo (currently
v2.0.20260427215009). Look up the matchingsha256digest for each image at that tag fromghcr.io/dependabot/dependabot-updater-<ecosystem>. If a digest is not resolvable, leave aTODOcomment and use the latest available pinned digest at the same tag family.Register them in
src/update-containers.tsin themanifestobject, alphabetically/grouped consistent with neighboring entries:Regenerate
docker/containers.jsonby running the project's own script — DO NOT hand-edit this file:Commit the regenerated
docker/containers.json.Search for any other places that enumerate ecosystems (tests, fixtures, docs/README, type definitions) and update them where appropriate. For example, search for existing ecosystem names like
"bun","bazel","docker_compose"to find lists that may need the new entries added.Required validation steps (run all of these and ensure they pass)
Per project convention these scripts must be run after the changes; commit any resulting artifact updates:
The
dist/directory is a checked-in build artifact for this Action — thenpm run packageoutput must be committed, otherwise the action will run stale code at runtime.Acceptance criteria
docker/Dockerfile.conda,docker/Dockerfile.deno,docker/Dockerfile.nixexist and follow the single-FROM-line pattern with a pinned tag andsha256digest.src/update-containers.tsmanifestobject containsconda,deno,nixkeys.docker/containers.jsonis regenerated vianpm run update-container-manifestand contains all three new entries.dist/is rebuilt vianpm run packageand committed.npm run format-check,npm run lint-check, andnpm testall pass.High-level PR description (use this in the PR body)
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: Create proper PR on
dependabot-actionsusing the project PR template and a...This pull request was created from Copilot chat.