[FEATURE] Renovate supporting `apm.yml`

[MPV]

Is your feature request related to a problem? Please describe.
Wouldn't it be nice if you could get automated pull requests for upgrading versions of dependencies in your apm.yml file?

Describe the solution you'd like
Work with Renovate (it's open source) on integrating support for APM.

Describe alternatives you've considered
Manually upgrading apm.yml when new versions of plugins arrive.

Additional context
I've raised a discussion over in Renovate for this as well (but they'll probably wish for someone to create the implementation):

• `apm.yml` (Agent Package Manager) renovatebot/renovate#42507

[MPV]

A first work item will be to fill in a "new package manager questionnaire" for Renovate as per:

• https://github.com/renovatebot/renovate/blob/main/docs/development/new-package-manager-template.md
• `apm.yml` (Agent Package Manager) renovatebot/renovate#42507 (comment)

[MPV]

I've drafted a reply, anyone up for reviewing before submission? Otherwise I'll submit this shortly:

New package manager questionnaire

Did you read our documentation on adding a package manager?

• I've read the adding a package manager documentation.

Basics

What's the name of the package manager?

APM (Agent Package Manager) — https://github.com/microsoft/apm

What language(s) does this package manager support?

APM is language-agnostic. It manages AI agent context (instructions, prompts, skills, hooks, MCP server declarations) for any project, regardless of the project's programming language. The tool itself is written in Python and distributed via PyPI (apm-cli).

The closest analogy is pre-commit or Terraform modules — a language-agnostic dependency manager that declares versioned dependencies on external git repos, resolves transitive graphs, and produces a lock file. But instead of git hooks or infrastructure, APM manages AI agent configuration.

How popular is this package manager?

• ~2 000 GitHub stars (as of April 2026). See live count.
• Published by Microsoft as an open-source project.
• Targets the fast-growing AI coding-agent ecosystem (GitHub Copilot, Claude Code, Cursor, OpenCode, Codex).
• Installable via pip install apm-cli, Homebrew, and platform-specific installers.

Does this language have other (competing?) package managers?

• Yes (give names).
• No.

There is no other widely adopted package manager for AI agent context. The space is new. Some adjacent tools exist but serve different purposes:

• Rules files / CLAUDE.md / .cursorrules — manual, per-project configuration files; no dependency resolution, versioning, or sharing.
• Copilot Extensions / MCP registries — provide runtime tool servers, not declarative dependency management for agent instructions and skills.
• gh skill CLI (docs, announcement) — GitHub CLI extension (v2.90.0+, preview) for installing, updating, searching, and publishing agent skills from GitHub repos. Follows the open Agent Skills specification (skills/*/SKILL.md convention). Supports version pinning (skill@v1.2.0 or skill@commitsha), 35+ agent hosts, and gh skill publish creates GitHub releases with semver tags. However, it is a flat file copier — skills are installed individually by copying SKILL.md directories to host-specific locations (e.g. .github/skills/). No manifest file, no lock file, no transitive dependency resolution, no multi-host compilation from a single source of truth. APM and gh skill operate at different layers: gh skill publish creates the semver-tagged GitHub releases that APM (and Renovate via git-tags) can consume as versioned dependencies.
• skills CLI / skills.sh (docs, source) — Vercel Labs-built open-source CLI (npx skills, ~15k GitHub stars) for the same Agent Skills ecosystem. Supports 44 agent hosts and sources from GitHub, GitLab, SSH URLs, and local paths. Installs skills via symlink (default) or copy to host-specific directories (e.g. .claude/skills/, .agents/skills/). Also reads .claude-plugin/marketplace.json for Claude plugin compatibility. Unlike gh skill, it has no version pinning — npx skills update always pulls the latest. Like gh skill, it is a flat file installer with no manifest, no lock file, and no dependency resolution. Has a discovery leaderboard at skills.sh based on anonymous install telemetry.
• Copilot CLI plugin system (docs) — GitHub Copilot CLI has a native plugin format with plugin.json manifest (searched at .plugin/plugin.json, .github/plugin/plugin.json, or .claude-plugin/plugin.json) and marketplace.json distribution. Plugin components include agents, skills, hooks, MCP servers, and LSP servers. Sources support github, url, git-subdir, and relative paths with ref/sha pinning. Installation via copilot plugin install PLUGIN@MARKETPLACE or OWNER/REPO. Default marketplaces: copilot-plugins and awesome-copilot. This is a distribution and runtime system, not a package manager — no transitive dependency resolution, no lock file, no multi-agent-runtime compilation. The marketplace.json schema is shared with Claude Code's plugin system (see below). APM auto-detects Copilot CLI plugins from all manifest locations and normalizes them into standard APM packages with full version locking and governance.
• Claude Code plugin system (docs) — Claude Code has its own native plugin format (.claude-plugin/plugin.json) with marketplace distribution (.claude-plugin/marketplace.json), /plugin install commands, and an official Anthropic marketplace (claude-plugins-official). Shares the same marketplace.json schema and nearly identical plugin.json manifest as Copilot CLI, but additionally supports npm as a plugin source type. Installation via /plugin install PLUGIN@MARKETPLACE. Like Copilot CLI, this is a distribution and runtime system — no transitive dependency resolution, no lock files with content-hash verification, no multi-agent-runtime compilation. APM bridges both plugin ecosystems bidirectionally: it auto-detects native plugins from either format, normalizes them into standard APM packages, and can export APM packages back to the plugin format via apm pack --format plugin.
• Codex plugin system (docs) — OpenAI Codex has a native plugin format (.codex-plugin/plugin.json) with skills, MCP servers, and app integrations (.app.json for external services like Gmail, Slack — unique to Codex). Marketplace at .agents/plugins/marketplace.json; also reads .claude-plugin/marketplace.json for cross-tool compatibility. Source types: local, url (git), and git-subdir with ref pinning. Adds installation policy fields (AVAILABLE, INSTALLED_BY_DEFAULT, NOT_AVAILABLE) and an interface block for visual presentation (icons, screenshots, brand color). CLI: codex plugin marketplace add OWNER/REPO. Shares the same core marketplace.json schema as Copilot CLI and Claude Code. Like both, this is a distribution and runtime system — no transitive dependency resolution, no lock file. Self-serve plugin publishing is not yet available.
• .well-known Agent Skills Discovery (agentskills/agentskills#254) — an emerging spec for HTTP-based skill discovery via /.well-known/agent-skills/index.json (RFC 8615). Distributes skills as SKILL.md files or archives with SHA-256 digests. This is a discovery/distribution mechanism, not a package manager — it has no dependency resolution, lock files, or transitive deps. APM already supports SKILL.md as a dependency type and could consume .well-known endpoints in the future.

APM is the only tool in this space that provides a manifest + lock file + transitive dependency resolution model.

What are the big selling points for this package manager?

• Reproducible agent context: lock file (apm.lock.yaml) pins every dependency to an exact git commit SHA, ensuring identical setups across machines.
• Multi-agent-runtime support: a single apm.yml compiles output for GitHub Copilot, Claude Code, Cursor, OpenCode, and Codex simultaneously.
• Git-native, registry-optional: packages are ordinary git repos (GitHub, GitLab, Bitbucket, Azure DevOps, self-hosted). No centralised registry is required.
• Transitive dependency resolution: full BFS dependency graph with circular-dependency detection, conflict resolution, and depth tracking.
• Enterprise governance: built-in policy engine (apm-policy.yml), supply-chain security auditing (apm audit), and content-hash verification.

Detecting package files

What kind of package files, and names, does this package manager use?

File	Format	Purpose
apm.yml	YAML 1.2	Package manifest (the equivalent of package.json)
apm.lock.yaml	YAML 1.2	Lock file (the equivalent of package-lock.json)

Both files live at the project root. The manifest filename is always exactly apm.yml — there is no alternate naming convention.

Which managerFilePatterns pattern(s) should Renovate use?

["/(^|/)apm\\.yml$/"]

Note: the lock file apm.lock.yaml lives alongside apm.yml and should be treated as an artifact that Renovate updates (see Artifacts), but does not need to be in managerFilePatterns itself.

Do many users need to extend the managerFilePatterns pattern for custom file names?

• Yes, provide details.
• No.

The manifest filename is always apm.yml. The specification does not allow alternate names.

Is the managerFilePatterns pattern going to get many "false hits" for files that have nothing to do with package management?

No. While apm.yml is a short name, its internal structure is distinctive (requires name and version top-level keys, and uses an apm/mcp-keyed dependencies block). A quick structural check (presence of dependencies.apm or dependencies.mcp) eliminates false positives.

Parsing and Extraction

Can package files have "local" links to each other that need to be resolved?

No. Each apm.yml is self-contained. Dependencies point to external git repositories (or local filesystem paths for development), not to other apm.yml files within the same repository.

Package file parsing method

The package files should be:

• Parsed together (in serial).
• Parsed independently.

Which format/syntax does the package file use?

• JSON
• TOML
• YAML
• Custom (explain below)

Standard YAML 1.2.

How should we parse the package files?

• Off the shelf parser.
• Using regex.
• Custom-parsed line by line.
• Other.

A standard YAML parser is sufficient. Dependencies live under well-defined keys (dependencies.apm, dependencies.mcp, devDependencies.apm, devDependencies.mcp).

Does the package file have different "types" of dependencies?

• Yes, production and development dependencies.
• No, all dependencies are treated the same.

APM has two axes of categorisation:

1. Production vs development: dependencies vs devDependencies (dev deps are excluded from apm pack --format plugin bundles).
2. APM vs MCP: each group has an apm list (git-hosted agent-context packages) and an mcp list (MCP server declarations).

For Renovate's purposes, the most relevant entries are under dependencies.apm and devDependencies.apm — these reference versioned git repositories.

List all the sources/syntaxes of dependencies that can be extracted

APM dependencies (dependencies.apm / devDependencies.apm) come in two forms:

1. String form:

dependencies:
  apm:
    # GitHub shorthand (default host)
    - microsoft/apm-sample-package              # latest default branch
    - microsoft/apm-sample-package#v1.0.0       # pinned to tag
    - microsoft/apm-sample-package#main         # branch ref

    # Non-GitHub hosts
    - gitlab.com/acme/coding-standards
    - bitbucket.org/team/repo#main

    # Full URLs
    - https://github.com/microsoft/apm-sample-package.git#v2.0.0
    - git@github.com:microsoft/apm-sample-package.git

    # Virtual packages (subdirectories/files within a repo)
    - ComposioHQ/awesome-claude-skills/brand-guidelines
    - contoso/prompts/review.prompt.md

    # Azure DevOps
    - dev.azure.com/org/project/_git/repo

    # Local path (development only — not relevant for Renovate)
    - ./packages/my-shared-skills

2. Object form:

dependencies:
  apm:
    - git: https://gitlab.com/acme/repo.git
      path: instructions/security
      ref: v2.0
      alias: acme-sec

In object form, ref carries the version (equivalent to the #ref fragment in string form). Renovate should update the ref value the same way it updates the #v1.0.0 fragment in string-form dependencies (e.g. ref: v2.0 → ref: v2.1.0).

Marketplace-resolved dependencies: APM has a marketplace system where curated plugin indexes (marketplace.json in GitHub repos) map plugin names to git sources. Users install via apm install code-review@acme-plugins on the CLI, but the resolved git URL is what gets written to apm.yml — Renovate will see standard owner/repo#ref entries, not marketplace syntax. The lock file carries provenance metadata (discovered_via, marketplace_plugin_name) but apm install manages those fields automatically.

MCP dependencies (dependencies.mcp / devDependencies.mcp) reference MCP servers. These are either registry-backed identifiers or self-defined server configs. They typically do not carry semver versions and are less relevant for Renovate initially.

Describe which types of dependencies above are supported and which will be implemented in future

Initial scope (recommended):

• dependencies.apm and devDependencies.apm entries that reference git repositories with a tag/version ref (e.g. owner/repo#v1.0.0). These have clear version semantics and are the primary use case for automated updates.

Future scope:

• dependencies.mcp — MCP server registry references. These may gain versioning as the MCP ecosystem matures.
• Dependencies pinned to branch names or commit SHAs — these could be updated to the latest commit on that branch, though the value proposition is lower.
• URL-based package installation (microsoft/apm#692, design phase) — would allow apm install https://example.com/packages/my-agent.tar.gz and introduce digest-pinned URL dependencies (#sha256:<hex>). If shipped, this would be a new dependency source type requiring its own lookup strategy. Not yet implemented.

Versioning

What versioning scheme does the package file(s) use?

Semantic Versioning (semver). The version field in apm.yml must match ^\d+\.\d+\.\d+ with optional pre-release/build suffixes (e.g. 1.0.0, 2.1.0-beta, 1.0.0+build123).

Dependency refs typically use git tags prefixed with v (e.g. #v1.0.0), matched by ^v?\d+\.\d+\.\d+.

Does this versioning scheme support range constraints, like ^1.0.0 or 1.x?

• Supports range constraints (for example: ^1.0.0 or 1.x), provide details.
• No.

APM does not support version ranges. Dependencies pin to an exact ref (tag, branch, or commit SHA). When no ref is specified, APM resolves to the latest default-branch commit and pins the exact SHA in the lock file.

This means Renovate would update a dependency by changing the ref value (e.g. #v1.0.0 → #v1.1.0) and letting apm install regenerate the lock file.

Lookup

Is a new datasource required?

• Yes, provide details.
• No.

APM dependencies are git repositories hosted on GitHub, GitLab, Bitbucket, Azure DevOps, etc. Renovate's existing datasources cover this — the manager would dynamically select the appropriate one based on the host in the dependency string:

Host	Datasource
github.com (explicit or implicit default)	github-tags
gitlab.com (or self-hosted GitLab)	gitlab-tags
All other hosts (Bitbucket, Azure DevOps, self-hosted)	git-tags (generic git ls-remote)

This is the same pattern used by the pre-commit manager. The manager should also declare versioning: "semver" since the git-tags datasource has no default versioning scheme.

Will users want (or need to) set a custom host or custom registry for Renovate's lookup?

• Yes, provide details.
• No.

APM supports any git-accessible host (GitHub, GitLab, Bitbucket, Azure DevOps, self-hosted instances). Users with dependencies on non-GitHub hosts will need Renovate to look up tags on the correct host.

Where can Renovate find the custom host/registry?

• No custom host or registry is needed.
• In the package file(s), provide details.
• In some other file inside the repository, provide details.
• User needs to configure Renovate where to find the information, provide details.

The host is encoded directly in the dependency string:

• gitlab.com/acme/coding-standards#v1.0.0 → host is gitlab.com
• bitbucket.org/team/repo#v2.0.0 → host is bitbucket.org
• microsoft/apm-sample-package#v1.0.0 → implicit host is github.com

Are there any constraints in the package files that Renovate should use in the lookup procedure?

• Yes, there are constraints on the parent language (for example: supports only Python v3.x), provide details.
• Yes, there are constraints on the parent platform (for example: only supports Linux, Windows, etc.), provide details.
• Yes, some other kind of constraint, provide details.
• No constraints.

Will users need the ability to configure language or other constraints using Renovate config?

• Yes, provide details.
• No.

Artifacts

Does the package manager use a lock file or checksum file?

• Yes, uses lock file.
• Yes, uses checksum file.
• Yes, uses lock file and checksum file.
• No lock file or checksum.

APM uses apm.lock.yaml (YAML 1.2). It records every dependency's exact commit SHA, deployed file paths, and content hashes. The lock file also tracks SHA-256 hashes of deployed files for integrity verification, but these are embedded in the lock file itself — there is no separate checksum file.

Is the locksum or checksum mandatory?

• Yes, locksum is mandatory.
• Yes, checksum is mandatory.
• Yes, lock file and checksum are mandatory.
• No mandatory locksum or checksum.
• Package manager does not use locksums or checksums.

The lock file is strongly recommended and should be committed to version control, but apm install works without a pre-existing lock file (it creates one). Enterprise policy rules can enforce lock file presence via apm audit.

If lockfiles or checksums are used: what tool and exact commands should Renovate use to update one (or more) package versions in a dependency file?

After Renovate modifies the version ref in apm.yml:

apm install

This re-resolves affected dependencies and updates apm.lock.yaml. For a full re-resolve of all dependencies:

apm install --update

Tooling: apm-cli is a Python package (pip install apm-cli). For Renovate's Containerbase-based environments (binarySource: install), apm-cli would need to be added to the Containerbase tool index. For binarySource: global, users pre-install it on the Renovate host.

Extraction-only fallback: If apm-cli is not available, Renovate can still operate in extraction-only mode — updating the ref in apm.yml without regenerating the lock file. Users would then run apm install in their own CI to update apm.lock.yaml. This matches how other managers degrade gracefully when their tool binary is missing.

Note: apm install writes cloned repositories to apm_modules/ (typically gitignored). Renovate should only commit changes to apm.yml and apm.lock.yaml, not the apm_modules/ directory.

Package manager cache

Does the package manager use a cache?

• Yes, provide details.
• No.

APM caches cloned git repositories in apm_modules/ within the project directory. On subsequent installs, it reuses cached repos and verifies content hashes from the lock file.

If the package manager uses a cache, how can Renovate control the cache?

• Package manager does not use a cache.
• Controlled via command line interface, provide details.
• Controlled via environment variables, provide details.

Running apm install --update forces a full re-resolve, bypassing cached commit SHAs. The apm_modules/ directory can also simply be deleted before install for a clean state.

Should Renovate keep a cache?

• Yes, ignore/disable the cache.
• No.

No special cache handling needed. Renovate modifies apm.yml, then runs apm install which handles caching internally.

Generating a lockfile from scratch

Renovate can perform "lock file maintenance" by getting the package manager to generate a lockfile from scratch.
Can the package manager generate a lockfile from scratch?

• Yes, explain which command Renovate should use to generate the lockfile.
• No, the package manager does not generate a lockfile from scratch.
• No, the package manager does not use lockfiles.

Delete the existing lock file and run:

rm -f apm.lock.yaml && apm install

This resolves all dependencies fresh and produces a new apm.lock.yaml.

Other

What else should we know about this package manager?

1. Git-tag-based versioning only — APM does not use a centralised package registry with its own version index. Versions are git tags. This aligns well with Renovate's existing git-tags datasource. Notably, gh skill publish (GitHub CLI) creates semver-tagged GitHub releases for skill repositories following the Agent Skills specification. These are the same tags that APM pins in apm.yml and that Renovate would update.

2. Virtual packages — a single dependency string can target a subdirectory or file within a larger monorepo (e.g. ComposioHQ/awesome-claude-skills/brand-guidelines). The version tag applies to the whole repository, not the subdirectory. Renovate should treat the base owner/repo as the versioned unit.

3. MCP dependencies are a separate concern — dependencies.mcp entries reference MCP (Model Context Protocol) servers. These are structurally different from APM deps and are not yet versioned in a way that lends itself to automated updates. They can be deferred to a future iteration.

4. Enterprise policy — organisations can define apm-policy.yml files that restrict allowed dependency sources, enforce lock file presence, and require content-hash verification. Renovate-generated PRs would need to pass these policy checks, but that happens naturally via apm install and CI.

5. Marketplace and Claude plugin interoperability — APM supports curated plugin marketplaces (marketplace.json indexes hosted as GitHub repos). Users can install plugins via apm install NAME@MARKETPLACE syntax. APM also auto-detects native Claude Code plugins (.claude-plugin/plugin.json) and Copilot CLI plugins, normalizing them into standard APM packages with full version locking and transitive resolution. In all cases, marketplace and plugin references are resolved to standard owner/repo#ref entries at install time and written to apm.yml in that canonical form. Renovate does not need to parse marketplace syntax or understand the plugin format — it will only encounter resolved git-based entries.

6. Emerging .well-known skill discovery and URL-based dependencies — The Agent Skills Discovery spec proposes HTTP-based skill distribution at /.well-known/agent-skills/index.json (skills as SKILL.md files or archives with SHA-256 digests). APM tracks this via microsoft/apm#554, but .well-known support is explicitly deferred pending upstream spec stability (still draft v0.2.0). Related in-flight work: #676 (PR #691) adds URL-based marketplace sources (remote marketplace.json URLs, git URLs with refs, local paths). A follow-up (#692, design phase) would enable direct URL-based package installation with digest pinning. If [FEATURE] URL-based marketplace work Extension #692 ships, it would introduce non-git dependency sources that may require a new Renovate datasource. For now, all APM dependencies resolve to git repositories.

7. Stable, versioned formats — The manifest schema and lock file format are versioned (lockfile_version: "1") and designed for forward compatibility. The project is under active development by Microsoft.

[MPV]

I submitted the above now, over at: 🤞

• `apm.yml` (Agent Package Manager) renovatebot/renovate#42507 (comment)

[github-actions]

Triage decision

needs-design

Proposed labels

theme/portability
area/marketplace
area/docs-site
type/feature
status/needs-design

Milestone

null

Suggested next action

Open a discussion or design doc with the Renovate maintainers defining: what constitutes a "version" for an APM package, the Renovate datasource/custom-manager strategy, and a recommended Renovate config for APM users that gates on PR review (not auto-merge).

Suggested issue comment

Welcome, and great feature request! Renovate integration would give APM users the same automated dependency-update workflow they already have for npm, pip, and cargo packages -- a natural fit for a package manager.

A few design questions need answers before this can land:

1. **What is a "version" for an APM package?** APM pins to git commit SHAs in `apm.lock.yaml`. Renovate typically works with semver tags. Does APM need to standardize on tagged releases for all packages, or can Renovate target the latest SHA on the default branch?

2. **Renovate integration shape**: the cleanest path is probably a Renovate [custom manager]((docs.renovatebot.com/redacted) that parses `apm.yml` dependency entries, paired with a custom datasource that resolves versions from GitHub. Alternatively, a first-party Renovate manager contribution upstream. Which path do you think is more maintainable?

3. **Auto-merge caution**: APM packages contain prompts, instructions, and agent definitions -- semantic changes that passing tests may not catch. We'd recommend APM users configure Renovate for PR-only (not auto-merge) for `apm.yml` updates. The Renovate config preset APM ships should enforce this default.

If you want to take the lead on the Renovate discussion and write up a design proposal, that would move this forward quickly. The APM maintainers are happy to collaborate on the upstream Renovate contribution once the shape is agreed.

Per-lens notes (collapsed)

DevX UX Expert -- User-Need Reviewer

Automated dependency updates via Renovate are the industry standard for npm/pip/cargo -- users rightly expect the same for APM. The request is short but points to a genuine gap in the APM lifecycle. The mental model is correct: Renovate creates PRs bumping versions in apm.yml, just like package.json. The UX concern is the auto-merge risk for semantic content (prompts, agent definitions) -- the default Renovate config APM ships should require human review.

Supply Chain Security Expert -- Risk-Surface Reviewer

Two supply chain considerations: (1) Renovate's version discovery mechanism must not be spoofable -- the datasource should use GitHub's authenticated API, not unauthenticated lookups that could be poisoned. (2) Auto-merged Renovate PRs could silently update agent definitions that contain prompts -- prompt injection via a compromised upstream package update is a real threat vector. The recommended Renovate config must explicitly set automerge: false for APM dependencies and require a human review step. Document this in the design.

OSS Growth Hacker -- Contributor-Tone Reviewer

Author's author_association is NONE -- first-time or low-interaction contributor. Tone is warm and invites them to lead the Renovate upstream discussion, which is a meaningful contribution path that does not require deep APM codebase knowledge. The reply names a concrete next step (write up the design proposal / start the Renovate discussion) so there is no ambiguity about how to move forward.

Python Architect -- Architecture Reviewer

For Renovate to support apm.yml, it needs: (a) a custom manager (regex or dedicated) that can parse APM's dependency format, and (b) a datasource that resolves "what versions exist" for an APM package. APM's current SHA-pinning model in apm.lock.yaml needs to be mapped to what Renovate understands as a "version". If packages are not consistently tagged, APM may need to introduce a versioning convention before Renovate integration is practical. This warrants a design doc before any code.

Doc Writer -- Documentation Reviewer

If implemented, Renovate integration needs a how-to guide in docs/src/content/docs/. area/docs-site secondary label is warranted. The guide should include the recommended Renovate config preset with automerge: false and a note on the semantic nature of APM package updates.

APM CEO -- Triage Arbiter

Strong enterprise signal -- Renovate is ubiquitous in enterprise CI pipelines. The direction is accepted but requires upstream coordination with Renovate and a versioning convention design. status/needs-design with no milestone is correct. The OSS Growth Hacker is right that inviting the author to lead the Renovate discussion is the best next step -- it's a high-value contribution path that does not require deep APM knowledge.

{
  "decision": "needs-design",
  "decision_detail": "Requires design covering: APM versioning convention compatible with Renovate, Renovate datasource/custom-manager strategy, and a default Renovate config preset with automerge:false for APM dependencies.",
  "theme": "theme/portability",
  "areas": ["area/marketplace", "area/docs-site"],
  "type": "type/feature",
  "status": "status/needs-design",
  "priority": null,
  "preserved_labels": [],
  "milestone": null,
  "next_action": "Open a design proposal defining what constitutes a 'version' for APM packages and the Renovate custom-manager/datasource strategy.",
  "comment_markdown": "Welcome, and great feature request! Renovate integration would give APM users the same automated dependency-update workflow they already have for npm, pip, and cargo packages -- a natural fit for a package manager.\n\nA few design questions need answers before this can land:\n\n1. **What is a \"version\" for an APM package?** APM pins to git commit SHAs in `apm.lock.yaml`. Renovate typically works with semver tags. Does APM need to standardize on tagged releases for all packages, or can Renovate target the latest SHA on the default branch?\n\n2. **Renovate integration shape**: the cleanest path is probably a Renovate [custom manager]((docs.renovatebot.com/redacted) that parses `apm.yml` dependency entries, paired with a custom datasource that resolves versions from GitHub. Alternatively, a first-party Renovate manager contribution upstream. Which path do you think is more maintainable?\n\n3. **Auto-merge caution**: APM packages contain prompts, instructions, and agent definitions -- semantic changes that passing tests may not catch. We'd recommend APM users configure Renovate for PR-only (not auto-merge) for `apm.yml` updates. The Renovate config preset APM ships should enforce this default.\n\nIf you want to take the lead on the Renovate discussion and write up a design proposal, that would move this forward quickly. The APM maintainers are happy to collaborate on the upstream Renovate contribution once the shape is agreed."
}

---

Triage status: agentic proposal pending human ratification.
Silence is approval. Maintainers can:

• Override any label or milestone above by editing it directly --
  human edits are authoritative and will not be reverted on
  subsequent runs.
• Re-trigger triage by applying the status/needs-triage label, or
  by removing status/triaged to enroll the issue in the next
  daily sweep.

Posted by the Triage Panel workflow. See .apm/skills/apm-triage-panel for the panel skill.

Generated by Triage Panel · ● 1.9M · ◷