How does `lock versions` work, as `.agents.lock` is gitignored?

[latel]

A package manager for .agents directories. Declare agent skill dependencies in agents.toml, lock versions for reproducibility, and share skills across your team.

As .agents.lockis gitignored, I really doubt howlock versions` works in CI.

[gricha]

Hey, yeah, I need to clean up the documentation, as it no longer locks in versions by default. We tested internally both versions and we landed on lock-by-default being much more cumbersome as, especially for internal dependencies that we mostly use, it would add unnecessary friction. Instead, if you want to pin specific skills to specific versions you can do it on a per-skill basis in agents.toml/when you're adding them.

The only reason .agents.lock is still around is because of support for wildcard/all skills from a repository. We support that so that if we add new skills to our main skills repo, they get automatically picked up by other repositories. .agents.lock is meant to track the expanded list of all skills for that purpose so that, when we need to remove some skills, you don't see untracked files in your local state. I think we may need to rename that file as .agents.lock suggests the actual package locking semantics which is no longer the case.

[AbhiPrasad]

yeah we ran into this when deploying this with more repos. Would really appreciate if we renamed the file, or updated the docs!