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
- Add the
apmentry todependabot.ymlin any repository where an agent installs skills or prompts through APM. A weekly schedule is a reasonable start; the changelog leaves the interval to you. - Review APM pull requests by hand. The update changes what your agent reads. Merge it the way you would merge a change to a system prompt, not the way you merge a patch-version bump in a test dependency.
- Do not drop your other checks. This change adds version tracking, not security coverage. Keep the package-name check and the install audit in place: audit auto-installed agent plugins before trusting what an agent installed, and keep upgrades behind a rollback so a bad update can be undone.
Limits
- This page rests on a single changelog entry, published November 3, 2026. No independent corroboration was found, and no Dependabot run was performed here, so the setup above is the changelog's setup, not a tested one.
- The changelog does not define which git dependencies count as supported, and does not say how Dependabot handles an
apm.ymlentry it cannot update. Anything beyond the changelog's wording would be guessing, and this page does not guess. - Version updates only. There are no security updates for APM in this change, and this page does not present it as security coverage.
Related playbooks
- Codex is now an official Termux package
- Claude Code subagent updates now cost 99% less
- Upgrade dependencies one package at a time, with a rollback for each
- Dependabot pauses alerts on quiet repos
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