v3.0.0 — Vocabulary alignment (ship-kit → release-kit)
v3.0.0 — Vocabulary alignment to PLATFORM ribbon (rename ship-kit → release-kit)
Breaking for v2.0.x consumers. Same marketplace structure, one kit renamed for vocabulary discipline against PLATFORM.md §6.1.
Why v3 right after v2
PLATFORM.md names the canonical SDLC ribbon as:
IDEATE · PLAN · CODE · BUILD · TEST · REVIEW · RELEASE · OPERATE
v2.0.x used ship-kit, which is non-canonical. At Lloyds we'll be teaching dev leads to navigate the platform by phase name — the marketplace plugin names must match the ribbon they're being taught from. Renaming now (while there are zero external consumers) is cheaper than carrying the alias forever.
Changes
| v2.0.1 | v3.0.0 |
|---|---|
plugins/ship-kit/ |
plugins/release-kit/ |
BUILD/RELEASE phase label |
RELEASE phase label (canonical) |
apm.yml version: 2.0.0 |
version: 3.0.0 |
Plugin pin: …/plugins/ship-kit#v2.0.1 |
…/plugins/release-kit#v3.0.0 |
All 5 plugins bump to 3.0.0 in lockstep (marketplace versioning convention — single source of truth for the bundle).
Action
dependencies:
apm:
- DevExpGbb/zava-agent-config/plugins/secure-baseline#v3.0.0
- DevExpGbb/zava-agent-config/plugins/code-kit#v3.0.0
- DevExpGbb/zava-agent-config/plugins/release-kit#v3.0.0
- DevExpGbb/zava-agent-config/plugins/operate-kit#v3.0.0
# ideate-kit if you author work upstream of code (PMs, architects)Then apm install. Lockfile entries become package_type: marketplace_plugin with virtual_path: plugins/<kit> and is_virtual: true.
Verified
- ✅
apm pack --offline→.claude-plugin/marketplace.json(5 packages) - ✅
apm audit --ci→ 18/18 checks pass - ✅
self-auditandapm-auditworkflows green onmain(commit381c962) - ✅ Storefront upgrade verified:
apm installintegrates 2 agents + 3 instructions + 2 skills
Future kits (additive, non-breaking)
plan-kit, build-kit, test-kit, review-kit will land in 3.x as content is authored against the remaining ribbon phases. Marketplace owner spec stays fixed.