Skip to content

v4.0.0 — symmetric .apm/<type>/ source layout

Choose a tag to compare

View all tags
@danielmeppiel danielmeppiel released this 06 May 12:25
· 23 commits to main since this release
v4.0.0
0240ae5

What changed

All 5 plugins (secure-baseline, ideate-kit, code-kit, release-kit, operate-kit) now use .apm/<type>/ uniformly across every primitive type (agents/, skills/, instructions/, commands/, hooks/).

Why

APM has an asymmetry between its pack-export and install-integrate code paths: pack accepts both .apm/<type>/ and root-level convention dirs, but install-time integrators only guarantee .apm/<type>/ for instructions, commands, and hooks (agents and skills tolerate root convention dirs). v3.0.0's mixed layout (agents/skills at plugin root, instructions in .apm/) worked but was fragile and inconsistent across the file tree. v4.0.0 standardizes on .apm/ — the only layout that works symmetrically through both code paths for every primitive type.

Migration

Pin @v4.0.0 instead of @v3.0.0:

dependencies:
  apm:
    - DevExpGbb/zava-agent-config/plugins/secure-baseline#v4.0.0
    - DevExpGbb/zava-agent-config/plugins/code-kit#v4.0.0
    - DevExpGbb/zava-agent-config/plugins/release-kit#v4.0.0
    - DevExpGbb/zava-agent-config/plugins/operate-kit#v4.0.0
    # plus ideate-kit if needed

No behavior change beyond the version bump. CI reusable workflow also pinned at @v4.0.0:

uses: DevExpGbb/zava-agent-config/.github/workflows/apm-audit.yml@v4.0.0

Verified

apm install from this tag deploys all 7 primitives correctly (2 agents, 2 skills, 3 instructions) into a downstream consumer.

Related

  • microsoft/apm#1161 — docs gap that motivated the layout standardization
  • v3.0.0 release for the prior release-kit rename + lockstep version bump
Assets 2
Loading