Maintenance

Accord Project dependency maintenance

Dependency snapshot: 2026-09-16.
This page tracks the Concerto v5 migration rollout status and remaining manual-review gates.

Current status

The producer stack is now published on Concerto 5:

• @accordproject/concerto-core / cto / util: 5.0.0
• @accordproject/concerto-codegen: 6.3.0
• @accordproject/markdown-transform: 1.1.0
• @accordproject/concerto-cli: 4.2.0 (v5-aligned line)
• @accordproject/cicero-core: 2.2.0
• @accordproject/template-engine: 5.1.0
• @accordproject/concerto-metamodel: 3.17.0 (unchanged, already compatible)

Most repository migrations have been merged. Remaining work is concentrated in PRs intentionally left open for manual review (test/fixture/code-adjustment policy).

Concerto v5 migration progress

Merged and released/synced

• accordproject/concerto#1324
• accordproject/concerto-docs#142
• accordproject/concerto-codegen#280 + release sync #281 (6.3.0)
• accordproject/markdown-transform#680 + release sync #681 (1.1.0)
• accordproject/concerto-cli#108 + release sync #109 (4.2.0)
• accordproject/template-archive#948 + release sync #949 (2.2.0)
• accordproject/template-engine#180 (5.1.0 line now live)

Merged (no package release step required)

• accordproject/concerto-conformance#36
• accordproject/vscode-web-extension#111
• accordproject/models#204
• accordproject/concerto-playground#69
• concerto-metamodel: no migration PR needed

Open manual-review PRs (intentionally not auto-merged)

Repository	PR	Why still open
concerto-dotnet	#57	Validator fixture changes
template-playground	#981	Runtime API + test expectation updates
apap	#254	Fixture/model generated test artifacts changed
cicero-template-library	#529	Source + fixture/test updates

All four are in manual-review mode by policy, with CI green/near-green at latest checks.

Stable package baseline

Package family	Repository	npm latest	Concerto compatibility	Required action
@accordproject/concerto-metamodel	concerto-metamodel	3.17.0	Compatible with Concerto 5	None
Concerto core family (core, cto, util, etc.)	concerto	5.0.0	Aligned on 5.x	None
@accordproject/concerto-codegen	concerto-codegen	6.3.0	Concerto 5-compatible	None
@accordproject/markdown-*	markdown-transform	1.1.0	Concerto 5-compatible	None
@accordproject/concerto-cli	concerto-cli	4.2.0	Concerto 5-compatible line	None
@accordproject/cicero-core / cicero-cli	template-archive	2.2.0	Concerto 5-compatible	None
@accordproject/template-engine	template-engine	5.1.0	Concerto 5-compatible	None

Remaining rollout actions

1. Manually review and merge open policy-gated PRs: concerto-dotnet#57, template-playground#981, apap#254, cicero-template-library#529.
2. Run any repository-specific post-merge release/deploy steps where applicable (for repositories that actually publish npm artifacts or deploy sites).

Upgrade dependency diagram (current)

flowchart TD
    C5["Concerto 5 family<br/>published"]
    CG["Codegen 6.3.0<br/>published"]
    MD["Markdown 1.1.0<br/>published"]
    CCLI["Concerto CLI 4.2.0<br/>published (v5-aligned)"]
    CICERO["Cicero Core 2.2.0<br/>published"]
    ENGINE["Template Engine 5.1.0<br/>published"]
    APPS["Consumer migrations<br/>mostly merged"]
    MANUAL["Manual review PRs:<br/>dotnet#57,<br/>template-playground#981,<br/>apap#254,<br/>library#529"]

    C5 --> CG
    C5 --> MD
    CG --> CCLI
    MD --> CICERO
    C5 --> CICERO
    CICERO --> ENGINE
    CG --> ENGINE
    MD --> ENGINE
    CCLI --> APPS
    ENGINE --> APPS
    APPS --> MANUAL

    classDef complete fill:#d9f7be,stroke:#389e0d,color:#135200;
    classDef review fill:#fffbe6,stroke:#d48806,color:#613400;
    class C5,CG,MD,CCLI,CICERO,ENGINE,APPS complete;
    class MANUAL review;

Loading

Maintenance rule after this migration

For patch/minor producer upgrades, update transitive consumers in dependency order. For future majors, re-run the organization inventory from npm metadata, verify peer ranges, and stage cycles with package-level sequencing before app upgrades.