Renovate + Dagger | Dagger | Page 1

azure shuttle Jan 21, 2026, 7:17 AM

#

🧵

#

The general idea would be to develop a plugin for Renovate, that can scan repos for dagger modules, and check their latest available versions?

final tree Jan 21, 2026, 8:05 AM

#

Yep that would be useful

#

That would allow us to keep our dependent modules up to date

#

Regular updates is the name of the game

#

@fervent fjord

azure shuttle Jan 21, 2026, 8:23 AM

#

dagger update will update all dependencies for the current module, in case that's useful

sharp lance Jan 21, 2026, 5:12 PM

#

I know that @thick wigeon had been working on this https://github.com/chrira/dagger-renovate, and possibly @left anchor investigated as well?

thick wigeon Jan 21, 2026, 6:41 PM

#

Yes, we use that renovate to update our modules with dagger develop. This updates the engine version and the SDK dependencies accordingly. I demoed it in a community call: #1370547151180009753 message
Updating module dependencies is not yet implemented.
I missed an API giving the latest version of a Daggerverse module. It is hard to find out the latest version when semver versioning is missing.

cosmic tundra Jan 21, 2026, 10:03 PM

#

We’re hitting a few issues with Renovate and Dagger.

We currently run Renovate via GitHub Action to mount the Docker socket, but I’d like to move this to our EKS cluster (I hit some issues when mounting the socket. This need a second look).

When Renovate runs dagger develop -r, it fails with: failed to resolve git src: git error: exit status. This is likely an SSH key issue during dependency installation.

{
  "name": “some-name-here”,
  "engineVersion": "v0.19.3",
  "sdk": {
    "source": "python"
  },
  "dependencies": [
    {
      "name": "secrets-file",
      "source": "git@github.com:some-org/repo-name/modules/secrets-file@0.112.1",
      "pin": "942006f1c1ac491042ac583589c05072c6b843ca"
    },

  ]
}

Also, updating a third-party Python dependency triggers the error below. I suspect it's because the generated code isn't committed to the repo.

Command failed: uv lock --upgrade-package google-cloud-artifact-registry
Using CPython 3.14.2 interpreter at: /opt/containerbase/tools/python/3.14.2/bin/python3
error: Distribution not found at: file:///tmp/renovate/repos/github/some-org/some-repo/daggerflows/some-module/.dagger/google-artifact-registry/sdk

final tree Jan 22, 2026, 12:13 AM

#

@cosmic tundra is with Nine (Brett) by the way

#

Good news is that we can probably run renovate normally ( not through gh actions ) when we start checking in the generated code.

#

Solomon mentioned that you can do that now... we should perhaps explore this

azure shuttle Jan 22, 2026, 12:33 AM

#

Also @final tree now that dagger functions can return changesets, with a nice UI for reviewing and applying them... And soon a first-class dagger generate to detect and run generator functions... Maybe we could implement such a generator function that updates all dependencies in the current context, then package that in a toolchain that anyone can install?

final tree Jan 22, 2026, 12:35 AM

#

Yes that would be good. Would this be a bit like dagger develop --recursive ?

final tree Jan 22, 2026, 12:21 PM

#

Does dagger cloud have an API we can call? If it did, would be possible to build a renovate datasource for it...

#Renovate + Dagger