Remove `--marketplace-output` flag in v0.15

[danielmeppiel]

Remove --marketplace-output flag in v0.15

TL;DR

--marketplace-output was deprecated in #1281 (silently Claude-only despite the format-agnostic name). Track its removal in v0.15 once the v0.14 replacement surface lands.

Background

PR #1281 introduced multi-profile marketplace outputs (claude, codex). The legacy --marketplace-output PATH flag was kept for backwards compatibility but now has a scope-narrowing footgun: it overrides only the Claude artifact, not "the marketplace output." The flag's help text was updated to "Marketplace legacy compatibility" but no runtime warning fires today, so CI scripts will silently regress when adopting outputs: [claude, codex].

The new surface designed in #1317 replaces it with format-symmetric affordances:

# Old
apm pack --marketplace-output ./build/x.json    # silently claude-only

# New (v0.14)
apm pack --output-path claude=./build/x.json    # explicit, format-named

Required before this can land

Depends on #1317 (v0.14 marketplace UX) shipping first:

• --output-path <format>=<path> and APM_MARKETPLACE_<FORMAT>_PATH env both available
• --marketplace-output has been emitting a real logger.warning(...) for one minor release cycle (v0.14)
• CHANGELOG migration line published in v0.14 announcing the v0.15 removal

Removal checklist (v0.15)

• Drop --marketplace-output Click option from src/apm_cli/commands/pack.py
• Remove marketplace_output field from BuildOptions and the orchestrator wiring
• Remove auto-translate shim and the deprecation warning
• Remove all references in:
  • docs/src/content/docs/reference/cli/pack.md
  • docs/src/content/docs/reference/cli-commands.md
  • docs/src/content/docs/producer/publish-to-a-marketplace.md
  • packages/apm-guide/.apm/skills/apm-usage/commands.md
• CHANGELOG entry under Breaking Changes for v0.15: name the flag, point to --output-path
• Delete unit tests scoped to --marketplace-output; the --output-path test suite should already cover the replacement contract

Migration line (for v0.15 release notes)

--marketplace-output PATH was removed. Use --output-path claude=PATH (deprecated since v0.14) or set marketplace.outputs.claude.path in apm.yml. The flag printed a deprecation warning in v0.14; CI scripts that suppressed warnings should be audited.

Why this is a separate tracker

Keeping the removal as its own issue prevents the v0.14 design issue from sitting open across the deprecation window. It also gives the breaking-change CHANGELOG entry a single durable URL to reference.

References

• feat(marketplace): support multi-profile marketplace outputs #1281 — multi-profile marketplace outputs (introduced the deprecation)
• Marketplace output UX: filter-driven CLI + map-based manifest + JSON output #1317 — v0.14 marketplace UX issue (defines the replacement surface)

[github-actions]

Triage decision

accept

Proposed labels

theme/portability
area/cli
area/marketplace
area/docs-site
type/refactor
status/accepted
breaking-change

Milestone

null (v0.15 milestone not yet verifiable; assign when milestone is created)

Suggested next action

Pick up the checklist in sequence: drop the Click option, remove BuildOptions.marketplace_output and its orchestrator wiring, delete the shim and warning, update the four named doc pages and commands.md, add the CHANGELOG breaking-change entry, and delete the scoped unit tests.

Suggested issue comment

Thanks for tracking this systematically. The v0.14 deprecation window (warning on every call + CHANGELOG migration line) is the right foundation for a v0.15 removal.

The checklist looks complete. A few pointers for whoever picks this up:

- `BuildOptions.marketplace_output` removal will surface any call sites the grep missed; run tests early.
- The four doc pages listed are the full scope -- the `commands.md` in `packages/apm-guide/.apm/skills/apm-usage/` is Rule-4-required and is already in the list.
- The CHANGELOG breaking-change entry should name the replacement flag (`--marketplace-path claude=PATH`) and the env var alternative (`APM_MARKETPLACE_CLAUDE_PATH`) that ships in v0.15 per #1317.

This is a `good first issue` candidate for a contributor comfortable with Click + dataclass refactors -- the blast radius is bounded and the checklist is ready to execute.

Per-lens notes (collapsed)

DevX UX Expert -- User-Need Reviewer

The --marketplace-output PATH flag was a UX footgun: its name implied format-agnostic control but it only overrode the Claude artifact, silently regressing CI scripts that adopted multi-profile outputs. The v0.14 replacement (--marketplace-path claude=PATH) is format-explicit and composable. The removal plan follows npm/cargo convention: one full minor with a runtime warning, a CHANGELOG migration line, and a named replacement. No UX concerns with the proposed approach.

Supply Chain Security Expert -- Risk-Surface Reviewer

No risk-surface implication. This removal touches the CLI flag layer and the BuildOptions data model only -- no lockfile, no auth, no signing, no download path, no integrity primitive is affected. The marketplace artifact paths themselves are not changing; only the flag that overrides them is being removed after one deprecation cycle.

OSS Growth Hacker -- Contributor-Tone Reviewer

Not activated -- author is a COLLABORATOR with established engagement on the repo; standard maintainer tone is appropriate.

Python Architect -- Architecture Reviewer

Removal is well-bounded: one Click option, one BuildOptions field, one auto-translate shim, and the associated unit tests. The replacement surface (#1317) is already shipped and tested. No cross-cutting interface design is needed before code can land; status/accepted is correct. The checklist already covers commands, data model, docs, tests, and CHANGELOG -- no additional design gate required.

Doc Writer -- Documentation Reviewer

Docs work is explicitly scoped in the issue body: cli/pack.md, cli-commands.md, publish-to-a-marketplace.md, and packages/apm-guide/.apm/skills/apm-usage/commands.md. All four are required by Rule 4 for a CLI flag removal. Adding area/docs-site as a secondary label so the implementing PR carries the reminder. The migration wording in the issue (--marketplace-output PATH was removed. Use --output-path claude=PATH) is clear and grounded in user vocabulary.

APM CEO -- Triage Arbiter

This is disciplined housekeeping: the author who designed the deprecation is now tracking its removal. All specialists agree -- no UX risk, no security surface, no architectural ambiguity. The breaking-change communication is already in the CHANGELOG (v0.14, #1317). Accepting with theme/portability (the change makes marketplace output format-agnostic and explicit) and priority/low (v0.15 window provides adequate runway). The issue is a strong good first issue candidate; the comment surfaces that.

{
  "decision": "accept",
  "decision_detail": "",
  "theme": "theme/portability",
  "areas": ["area/cli", "area/marketplace", "area/docs-site"],
  "type": "type/refactor",
  "status": "status/accepted",
  "priority": "priority/low",
  "preserved_labels": ["breaking-change"],
  "milestone": null,
  "next_action": "Pick up the checklist in sequence: drop the Click option, remove BuildOptions.marketplace_output and its orchestrator wiring, delete the shim and warning, update the four named doc pages, add the CHANGELOG breaking-change entry, and delete the scoped unit tests.",
  "comment_markdown": "Thanks for tracking this systematically. The v0.14 deprecation window (warning on every call + CHANGELOG migration line) is the right foundation for a v0.15 removal.\n\nThe checklist looks complete. A few pointers for whoever picks this up:\n\n- `BuildOptions.marketplace_output` removal will surface any call sites the grep missed; run tests early.\n- The four doc pages listed are the full scope -- the `commands.md` in `packages/apm-guide/.apm/skills/apm-usage/` is Rule-4-required and is already in the list.\n- The CHANGELOG breaking-change entry should name the replacement flag (`--marketplace-path claude=PATH`) and the env var alternative (`APM_MARKETPLACE_CLAUDE_PATH`) that ships in v0.15 per #1317.\n\nThis is a `good first issue` candidate for a contributor comfortable with Click + dataclass refactors -- the blast radius is bounded and the checklist is ready to execute."
}

---

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.

Note

🔒 Integrity filter blocked 23 items

The following items were blocked because they don't meet the GitHub integrity level.

• #1120 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1122 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1130 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1138 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1156 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1157 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1209 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1225 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1231 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1266 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1273 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1279 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1293 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1295 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1297 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1300 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 7 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Triage Panel · ● 651.7K · ◷