Skip to content

update: bump microsoft/apm to 0.35.1 - #426

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/microsoft-apm-0.x
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/microsoft-apm-0.x

Conversation

@renovate

@renovate renovate Bot commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
microsoft/apm patch 0.35.0 → 0.35.1

Release Notes

microsoft/apm

v0.35.1

Compare Source

Changed
  • APM-owned software, agent primitives, code examples and OpenAPM are now licensed under Apache-2.0, with general documentation under CC-BY-4.0; historical MIT and third-party notices are preserved. Redistributors should review the new terms and retain notices when updating; earlier MIT releases are unchanged. (#​3487)
  • MAINTAINERS.md now lists the project maintainers, replacing the duplicate AUTHORS file; contributor credit moves to CONTRIBUTING.md and governance approval remits are unchanged. (#​3489)
Fixed
  • apm install now stops before stale-file cleanup and lockfile replacement when missing local receipts block a skill deployment, so cold --frozen replay with overlapping dependencies keeps the refused files and the prior lock contents. Move conflicting files aside before retrying, or use --force only to overwrite them intentionally. -- with credit to @​TyceHerrman (#​3440, #​3490)
  • apm install deploys a skill into a pre-existing empty (or nested-empty) skill directory and records it in apm.lock.yaml, instead of reporting success while skipping it; directories holding any file or symlink are still treated as unmanaged content. -- by @​MohammedAlkindi (#​3449)
  • apm install refuses an unmatched skills: selection before writing any of that dependency's primitives, so the failed install no longer rewrites its instructions or other deployed files. (#​3538)
  • apm install PKG and apm install -g PKG now remove dependencies the named package no longer declares, and nothing else installed needs, from apm.lock.yaml, apm_modules/ and deployed files; unrelated packages' lock entries are untouched and shared dependencies are kept. (#​3528)
  • apm install --frozen now deploys the locked release for Git-semver dependencies already in apm_modules (such as owner/repo/packages/pkg#^1.0.0), and repeat installs keep constraint, resolved_tag and resolved_ref instead of recording the raw range. (#​3527)
  • Unchanged apm install no longer rewrites generated_at in a committed v2 or v3 apm.lock.yaml when a SHA-pinned dependency carries resolved_tag; changed refs still update the lock. (#​3536)
  • apm lock, apm install and other lockfile writers now fail with an error naming the link and its target when apm.lock.yaml is a symlink, instead of silently replacing the link with a regular file; the link and target are left unchanged. (#​3532)
  • apm install and apm compile create a new apm.lock.yaml and compiled outputs such as AGENTS.md with umask-derived permissions (-rw-r--r-- under umask 022) instead of owner-only 0600; existing files keep their mode and secret-bearing configs stay 0600. (#​3547)
  • apm install -g into one Claude profile (CLAUDE_CONFIG_DIR) or Hermes home (HERMES_HOME) no longer deletes files deployed to another profile through the shared user lockfile; stale-file cleanup is limited to the selected root. -- by @​xronos-i-am (#​3424)
  • apm uninstall -g under a Claude profile (CLAUDE_CONFIG_DIR) removes the package's files and lockfile rows only from that profile instead of deleting the default profile's files; a package another profile still uses stays in ~/.apm/apm.yml until it is uninstalled from every profile. (#​3555)
  • apm install and apm install -g no longer fail with "installation binding does not match" after a reboot or remount changes only the root's device number on Linux (btrfs subvolumes) and macOS; the receipt is rebound when inode, path, installation identity and recorded creation time still match, and recreated roots stay rejected. -- by @​TyceHerrman (#​3439)
  • Antigravity rules now follow Antigravity's documented schema: multi-pattern applyTo becomes one quoted comma-separated globs string instead of a list Antigravity rejects, and instructions without applyTo get trigger: always_on so Antigravity no longer discards them. Affected .agents/rules/*.md files and their lockfile hashes update on the next non-frozen apm install; OpenAPM req-tg-005 is amended to match. (#​3546)
  • A timed-out HTTP lifecycle hook whose response arrives during the post-abort grace window now closes that response instead of leaking its connection; the deadline error log is unchanged. (#​3548)
  • apm mcp search and apm mcp show now display the server version from MCP Registry v0.1 records (top-level server.version) instead of -- / Unknown; legacy version_detail records render as before. (#​3549)
  • A warm-cache apm install --frozen keeps a Codex compatibility dependency's locked full commit as its source pin instead of the cached sentinel that native admission rejected; caches without a full locked commit still fail closed. -- by @​abhishekacharya200 (#​3407)
  • apm deps tree places transitive dependencies under the declaring package when sibling subdirectory packages from one repository share a parent, instead of listing them as could not place in tree; apm deps why names subdirectory parents by their full path. (#​3537)
  • MCP Registry OCI packages whose runtimeArguments carry only Docker options now render docker run -i --rm <options> <image> <args> for Codex, Copilot, Gemini and VS Code instead of an argv Docker rejects or an empty VS Code entry; explicit run and empty arguments render unchanged. -- by @​abhishekacharya200 (#​3405)
  • apm lock, apm install and other lockfile writers now fail with an error naming the link and its target when apm.lock.yaml is a symlink, instead of silently replacing the link with a regular file; the link and target are left unchanged. (#​3532)
  • Unchanged apm install no longer rewrites generated_at in a committed v2 or v3 apm.lock.yaml when a SHA-pinned dependency carries resolved_tag; changed refs still update the lock. (#​3536)
  • apm install deploys a skill into a pre-existing empty (or nested-empty) skill directory and records it in apm.lock.yaml, instead of reporting success while skipping it; directories holding any file or symlink are still treated as unmanaged content. -- by @​MohammedAlkindi (#​3449)
  • apm audit --ci cold replay now fetches git@ and ssh:// dependencies over SSH, matching apm install, so private SSH-only packages no longer need APM_GIT_PROTOCOL=ssh for audit. HTTPS and shorthand selection and the strict no-fallback default are unchanged. (#PR)
  • apm audit --ci cold replay now fetches git@ and ssh:// dependencies over SSH, matching apm install, so private SSH-only packages no longer need APM_GIT_PROTOCOL=ssh for audit. HTTPS and shorthand selection and the strict no-fallback default are unchanged. (#​3531)
  • A zero or negative lifecycle script timeoutSec or timeout now falls back to the per-type default (30s command, 10s http) with a warning naming the script, so both spellings behave the same. (#​3544)
  • install.ps1 now prints the full output of a failed staged-binary --version check, so Windows PowerShell 5.1 users see the whole Python traceback instead of only its first line. (#​3533)
  • apm install PKG and apm install -g PKG now remove dependencies the named package no longer declares, and nothing else installed needs, from apm.lock.yaml, apm_modules/ and deployed files; unrelated packages' lock entries are untouched and shared dependencies are kept. (#​3528)
  • apm install refuses an unmatched skills: selection before writing any of that dependency's primitives, so the failed install no longer rewrites its instructions or other deployed files. (#​3538)
  • apm install --frozen now deploys the locked release for Git-semver dependencies already in apm_modules (such as owner/repo/packages/pkg#^1.0.0), and repeat installs keep constraint, resolved_tag and resolved_ref instead of recording the raw range. (#​3527)
  • On Windows, apm install and apm update no longer fail when a scanner or indexer briefly holds a staged package during activation (WinError 5/32): the activation rename and its restore now retry with bounded backoff, while persistent denials still fail with the original error and recovery data preserved. (#​3530)
  • The uncached Git fallback pins core.autocrlf=false on both its working-tree clone and the checkout that follows, so a host whose gitconfig sets core.autocrlf=true no longer materializes CRLF bytes and then fails apm install with "Your local changes would be overwritten by checkout" when the locked commit differs from the branch head. -- by @​abhishekacharya200 (#​3409)
  • Registry-only mode (PROXY_REGISTRY_ONLY) no longer contacts the upstream host to enumerate refs or versions, while exact tags and locked resolutions still install through the proxy. Semver ranges and apm view <pkg> versions now fail with an actionable error, and apm outdated reports git dependencies as unknown with the remedy. -- by @​pearlatvg (#​3471)
  • Repeated apm compile runs on unchanged sources now keep the same placement: AGENTS.md, CLAUDE.md and GEMINI.md files written by an earlier compile (marked as APM-generated) no longer count as applyTo matches. Previously, sparse subtrees could switch to root-inline placement and show a permanent orphan warning for the compiler's own output. (#​3539)
  • apm audit --ci cold replay now fetches git@ and ssh:// dependencies over SSH, matching apm install, so private SSH-only packages no longer need APM_GIT_PROTOCOL=ssh for audit. HTTPS and shorthand selection and the strict no-fallback default are unchanged. (#​3531)
  • apm audit recognizes GitHub Copilot's documented sessionStart prompt hook ("type": "prompt") and scans its prompt text instead of failing with incomplete coverage; prompt handlers on other Copilot events, unknown handler types and non-string prompts still fail closed. (#​3542)
  • Self-defined MCP servers whose names contain a slash, such as com.example/server, now keep their declared name as the config key in every target instead of colliding on the final segment; registry, @scope/name and plain names are unchanged. An older truncated entry is replaced only when APM's ownership records prove it wrote it; otherwise it is left in place. -- by @​bodapatisaikrishna (#​3493)
  • Claude plugin .mcp.json files in the flat top-level server-map shape (as in linear, github and playwright from anthropics/claude-plugins-official) now install their MCP servers like the {"mcpServers": {...}} shape; a plugin MCP file with no usable server now warns, naming the file, instead of being silently ignored. (#​3541)
  • MCP servers declared by a Claude plugin installed from a local path (.mcp.json or plugin.json mcpServers) now deploy to the selected targets like the same plugin installed from git, with the same policy, lockfile ownership and uninstall cleanup. APM warns instead of silently dropping them when the plugin's synthesized manifest is missing. (#​3540)
  • MCP Registry OCI packages whose runtimeArguments carry only Docker options now render docker run -i --rm <options> <image> <args> for Codex, Copilot, Gemini and VS Code instead of an argv Docker rejects or an empty VS Code entry; explicit run and empty arguments render unchanged. -- by @​abhishekacharya200 (#​3405)
  • apm mcp search and apm mcp show now display the server version from MCP Registry v0.1 records (top-level server.version) instead of -- / Unknown; legacy version_detail records render as before. (#​3549)
  • Codex compatibility bundles install again with current Codex releases: native registration now requires Codex CLI 0.163.0 or later instead of exactly 0.163.0. Older or unrecognized versions are refused with the minimum named, and unexpected app-server responses still fail before any native write. (#​3529)
  • Codex project-scope stdio MCP env values declared as KEY: ${KEY} or KEY: ${env:KEY} are written as env_vars in .codex/config.toml instead of resolved secrets, with a names-only warning for other references -- by @​abhishekacharya200 (#​3406)
  • A warm-cache apm install --frozen keeps a Codex compatibility dependency's locked full commit as its source pin instead of the cached sentinel that native admission rejected; caches without a full locked commit still fail closed. -- by @​abhishekacharya200 (#​3407)
  • apm marketplace check accepts a ref that is a full 40-character commit SHA when the remote serves that commit, matching apm pack, instead of failing with Ref '<sha>' not found; unreachable commits and abbreviated SHAs fail with an actionable message, and tag and branch refs are unchanged. (#​3543)
  • A zero or negative lifecycle script timeoutSec or timeout now falls back to the per-type default (30s command, 10s http) with a warning naming the script, so both spellings behave the same. (#​3544)
  • A timed-out HTTP lifecycle hook whose response arrives during the post-abort grace window now closes that response instead of leaking its connection; the deadline error log is unchanged. (#​3548)
  • install.ps1 now prints the full output of a failed staged-binary --version check, so Windows PowerShell 5.1 users see the whole Python traceback instead of only its first line. (#​3533)
  • Scoop install instructions in the README, docs and apm-usage skill now use Scoop's default main bucket instead of the dead microsoft/scoop-apm bucket. (#​3517)
  • Prompt authoring, copilot target and packaged apm-usage docs now state that .github/prompts/ files load only in VS Code Local harness sessions, not the Copilot harness or Copilot CLI, and show the skill alternative with disable-model-invocation: true; prompt deployment is unchanged. (#​3550)
  • The devcontainer README no longer advertises the ghcr.io/microsoft/apm/apm-cli feature, which is not published to GHCR, and points to the supported ways to use APM in a dev container. (#​3526)
  • The lockfile spec now shows deployed_file_hashes and local_deployed_file_hashes values in the sha256:<hex> form APM writes instead of bare hex. (#​3519)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions

Copy link
Copy Markdown

TL;DR for garyj

  • Patch release, mostly bugfixes and docs; nothing breaking, safe to merge.
  • Relicensing: APM-owned code/examples and OpenAPM now Apache-2.0 (docs CC-BY-4.0); worth a glance if you redistribute or fork any of it.
  • apm.lock.yaml now fails loudly instead of silently replacing a symlink, and file perms on generated lockfiles/outputs follow umask (0644) instead of forced 0600 — only secret-bearing configs stay 0600.
  • apm install PKG now properly prunes dependencies the package no longer declares, including from apm_modules/ and deployed files — tighter lockfile hygiene if you use apm for skill/agent dependency management.
  • Linux-relevant fix: install/uninstall no longer misfires after a btrfs subvolume remount changes the root device number (previously broke the installation binding check).
  • Minor but handy: apm mcp search/show now surfaces real server versions from MCP Registry v0.1 records instead of Unknown.

0.35.1

  • As above — nothing further to flag beyond the lockfile/permission and dependency-pruning fixes.

Auto-summarized by claude-sonnet-5 from the release notes above. Add/remove the deps-summary label to control this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant