Problem
APM documents skills/<name>/SKILL.md as a supported repository layout for a
collection of skills. Each skill can also be a hybrid package with its own
apm.yml.
microsoft/apm-action@v1 with mode: release currently detects an aggregator
only when it finds plugins/<name>/apm.yml. A repository containing
skills/<name>/apm.yml is classified as single-plugin, so release mode reads
and packs only the root apm.yml instead of discovering the individual skill
packages.
The relevant implementation is detectShape() and discoverPackages() in
src/release.ts.
Generic reproduction
collection/
├── apm.yml
└── skills/
├── alpha/
│ ├── SKILL.md
│ └── apm.yml
└── beta/
├── SKILL.md
└── apm.yml
Run the documented tag-triggered release workflow:
- uses: microsoft/apm-action@v1
with:
mode: release
release-skip-publish: true
The action reports single-plugin and discovers the root package rather than
alpha and beta.
Expected behavior
Release mode should support APM's multi-skill collection layout, either by
discovering skills/*/apm.yml or through an explicit package-path or glob input
that avoids ambiguous shape inference.
Relevant APM package-layout documentation:
https://github.com/microsoft/apm/blob/main/packages/apm-guide/.apm/skills/apm-usage/package-authoring.md
Problem
APM documents
skills/<name>/SKILL.mdas a supported repository layout for acollection of skills. Each skill can also be a hybrid package with its own
apm.yml.microsoft/apm-action@v1withmode: releasecurrently detects an aggregatoronly when it finds
plugins/<name>/apm.yml. A repository containingskills/<name>/apm.ymlis classified assingle-plugin, so release mode readsand packs only the root
apm.ymlinstead of discovering the individual skillpackages.
The relevant implementation is
detectShape()anddiscoverPackages()insrc/release.ts.Generic reproduction
Run the documented tag-triggered release workflow:
The action reports
single-pluginand discovers the root package rather thanalphaandbeta.Expected behavior
Release mode should support APM's multi-skill collection layout, either by
discovering
skills/*/apm.ymlor through an explicit package-path or glob inputthat avoids ambiguous shape inference.
Relevant APM package-layout documentation:
https://github.com/microsoft/apm/blob/main/packages/apm-guide/.apm/skills/apm-usage/package-authoring.md