AI Development Tools 6 min read Published 2026-11-12

Dependabot APM updates: lockfiles, supported dependencies and beta errors

Dependabot can open version-update pull requests for supported Git dependencies in APM, helping teams keep shared skills, prompts and instructions current. Check your apm.yml entries and existing lockfile first. This support excludes security updates, and a pull request does not mean new instructions have been reviewed or put into use.

GitHub Dependabot APM Agent dependencies Lockfiles

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

GitHub announced general availability for all GitHub.com plans on November 3. Its announcement describes GHES 3.24 support as forthcoming; that does not establish availability on a particular self-hosted instance.
Supported Git dependency strings under dependencies.apm and devDependencies.apm can be updated. Tags, full commit SHAs and branches follow different rules.
An existing apm.lock.yaml is regenerated; a missing one is not created. Branch updates require that lockfile to exist.
GA does not require the old beta flag. A fix removing the APM beta check has merged following public reports, but recovery in a particular repository still needs verification.

Which repositories can start using it?

APM, or Agent Package Manager, manages dependencies such as agent skills, prompts and instructions. On November 3, 2026, GitHub announced that Dependabot can open version-update pull requests for supported Git dependencies in apm.yml. The feature is generally available on GitHub.com across all GitHub plans; the announcement does not discuss separate pricing.

The same announcement says support will be available in GitHub Enterprise Server 3.24. That future commitment does not establish support on every GHES instance. Self-hosted teams should check their version and its release notes. This article reviews public sources as of November 12 in Asia/Shanghai; no private repository or account was tested.

The stated scope is version updates, not security updates. A proposed dependency revision does not establish that prompt vulnerabilities were scanned, that instructions are safe or that security problems were automatically fixed.

How do tags, full SHAs and branches update?

Dependabot reads dependencies.apm and devDependencies.apm. Semantic Versioning tags, such as v1.0.0, update to the latest SemVer tag. Both plain and package-scoped tags are supported. A package-scoped tag must begin with the package name: the repository name or the last component of a virtual package path, as in octo-org/octo-skills/skills/review#review-v1.4.0.

An entry pinned to a full 40-character commit SHA updates to the commit of the latest annotated, non-prerelease release tag, with the tag name added as a comment. Abbreviated SHAs are unsupported. This rule does not mean tracking whichever commit happens to be newest.

A branch entry, such as octo-org/octo-skills#main, updates to the latest commit on that branch. The manifest still names the branch, so only apm.lock.yaml changes. That file must already exist.

Why did neither the branch nor a new lockfile appear?

When apm.lock.yaml exists, Dependabot regenerates it through apm lock. It does not create a missing lockfile. First decide whether you expect a tag change in the manifest or a branch-commit change in the lockfile, then inspect the relevant file differences.

Consider an unexecuted example: a team adds octo-org/octo-skills#main to apm.yml without committing a lockfile. Under the documented rules, it cannot expect Dependabot to create that lockfile and begin tracking branch commits. A maintainer should prepare, review and commit the lockfile through the normal APM process, then verify later updates.

Conversely, a manifest that still says main while the locked commit changes may be behaving exactly as intended. Review the changes anyway: a lockfile-only diff can still change the skill content that the project uses.

Which dependency entries are skipped?

The current documentation excludes object-form git:, registry:, id: and path: maps, plus mcp: entries. Entries without a ref, local paths and Azure DevOps-hosted entries are also excluded. Other unsupported forms include http:// or git:// clone URLs, YAML block scalars, quoted strings containing escape sequences and abbreviated commit SHAs.

When apm.yml sets registries.default, shorthand entries such as octo-org/octo-skills#v1.2.0 are not updated. Explicit clone-URL entries can still be updated, subject to the protocol and syntax restrictions above. Recognizing a repository does not mean every dependency inside it is supported.

Private Git dependencies use Dependabot git registry authorization. Detecting the manifest does not grant access to a dependency repository. An authorized maintainer should configure private access through the official documentation; keep credentials out of skill files and public issues.

How do you configure it and verify an update?

In the updates list in .github/dependabot.yml, add an entry with package-ecosystem set to apm, directory pointing to the folder containing apm.yml, and a chosen schedule. The directory is the manifest location, not the folder where downloaded skills end up. Preserve any existing ecosystem entries.

Check those three settings, then compare dependency syntax, refs and the lockfile against the supported forms. Inspect the actual Dependabot run and pull-request diff. If no pull request appears, distinguish no available revision from an unsupported entry, missing authorization or a run error before concluding that nothing ran.

A pull request is a proposed change. Review old and new skills, prompts and instructions for behavior and permission changes, validate them through your normal process, then merge and check the version the project actually uses. Creating a pull request, merging it and an agent loading new instructions are different pieces of evidence.

Why might a GA feature still request a beta flag?

The APM support discussion stated on November 6 that enable-beta-ecosystems: true was no longer required after GA. However, public issue #16879 reported on November 10 that GitHub.com still requested it, and that adding it did not produce the expected updates. This is a specific user report, not evidence that every repository was affected.

Pull request #16885, which removes the APM beta check, merged on November 10 at 20:44:02 UTC. The issue discussion pointed to it as the expected fix on November 11. A merged change and a closed issue do not establish deployment in your execution environment or resolution of every no-update problem.

If you still see the error, retain a sanitized run time, ecosystem, manifest directory and exact error, then compare current documentation and issue progress. Do not treat the old beta flag as a permanent requirement. If the run succeeds without an update, continue checking the dependency and lockfile rules above.

Sources

Frequently Asked Questions

Can I rely on the old discussion saying APM has no lockfile?

No. The original request in #14350 dates to March 2026 and reflects the user’s question at that time. Current documentation explicitly describes apm.lock.yaml regeneration and branch-update rules. Use current documentation and actual repository files to assess today’s behavior.

Are APM updates connected to pausing alerts on inactive repositories?

These are separate mechanisms. This article covers version-update pull requests; a different November 10 announcement concerns a future pause in Dependabot vulnerability alerts on some inactive repositories. Alert status does not establish whether APM updates are enabled, and an APM pull request does not establish that security alerts have resumed.

Can changing a proxy or network exit make unsupported APM entries update?

It cannot change ecosystem coverage, GitHub plan eligibility, GHES versions or private-repository permissions. Investigate networking separately when there is an actual connection error. Reachability alone does not establish correct configuration or authorization.