Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Dependabot now updates agent package managers

Written November 8, 2026

Dependabot updates now cover git dependencies in apm.yml. What it tracks, what it doesn't — no security updates — and how to wire it into an agent setup.

What it does

Dependabot version updates now support Agent Package Manager. Dependabot opens pull requests to update supported git dependencies declared in apm.yml, and regenerates apm.lock.yaml when one is present. The point is the agent's own supply chain: skills, prompts, and instructions installed through APM are pinned dependencies like any other, and they drift the same way. A skill pinned six months ago stays pinned until something updates it, and now that something can be Dependabot.

Support is generally available on github.com for all GitHub plans, and will be available in GitHub Enterprise Server 3.24. The changelog is dated November 3, 2026, and it is the only source for this page. No independent write-up or test of the feature was found, so everything below comes from that one changelog entry.

What it does not do

The limit is in the changelog's own sentence: this support covers version updates, not security updates. That distinction matters more here than it does for ordinary dependencies, because the thing being updated is the material an agent reads and follows. A version update moves a skill or prompt to a newer release. It does not tell you whether the old version had a known vulnerability, and it does not patch one. A builder who assumes Dependabot is now watching agent packages for security problems will be unpleasantly surprised: that coverage does not exist in this change.

The scope is also narrow in a second way. Dependabot updates supported git dependencies declared in apm.yml. Dependencies that are not git dependencies are out of scope, and the changelog does not say which git dependencies count as supported beyond that. If a line in your apm.yml is not a supported git dependency, Dependabot will not open a pull request for it, and nothing on the changelog page says otherwise.

Wiring it up

The setup follows the ordinary Dependabot pattern. Add an apm entry to your .github/dependabot.yml file, specify the directory containing apm.yml, and choose an update schedule:

version: 2
updates:
  - package-ecosystem: "apm"
    directory: "/"
    schedule:
      interval: "weekly"

From there, Dependabot watches apm.yml like any other manifest and opens pull requests when a supported git dependency has a newer version. Treat those pull requests the way you would treat any agent-facing change: read the diff before merging, because the thing being updated is instructions your agent will follow. A skill update that changes a prompt's behaviour is a behaviour change in your agent, not just a version bump. If your repository has an apm.lock.yaml, Dependabot regenerates it as part of the update, so the lockfile stays in step with the manifest.

What to do with it

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Check every package name your agent invents · MCP reference servers 2.3.0: what's new · Audit apps that installed agent plugins for you