Manage versions and deprecation

Providers change their APIs on their schedule. Version management is how you absorb that on yours — running old and new side by side, warning consumers before anything moves, and removing a version only once nothing depends on it.

Run more than one version

A service holds a list of enabled versions. Add one and the old one keeps working.

fused-cli service version <add|remove|deprecate> <service-slug> <version>

Only the last two are yours — the service slug and the provider’s version string.

fused-cli service version add stripe 2024-06-20
fused-cli service version list stripe
fused-cli workspace plan
fused-cli workspace apply

In workspace.yaml, versions is a list of objects, one per enabled version — not a list of version strings:

services:
  stripe:
    versions:
      - version: "2024-04-10"
      - version: "2024-06-20"

Anything scoped to a version — visibility, execution policy, connection profiles — nests inside that version’s entry. Flat version strings fail to parse, which is deliberate: it stops a policy from drifting away from the version it belongs to.

Announce a deprecation

A deprecation is advisory. It records intent — a date and a reason — while the service stays fully active, so existing SDK and MCP configs keep working while their owners migrate.

fused-cli service deprecate stripe \
  --at 2026-12-01 \
  --reason "Provider retires this version"

fused-cli service version deprecate stripe 2024-04-10 \
  --at 2026-12-01 \
  --reason "Superseded by 2024-06-20"

Nothing is cut off on the date you set. There is no automatic date-triggered removal. Treat --at as the date you intend to run the delete, once you have confirmed nothing still depends on it.

Remove it for real

Removal is a separate, deliberate step.

fused-cli service version remove stripe 2024-04-10
fused-cli service remove stripe

If any SDK or MCP config in the same Registry account still references what you are removing, the plan comes back with a blocker instead of quietly breaking those configs. --force accepts that and removes it anyway — and writes a workspace_service_removed or workspace_version_removed notification recording that you made the call.

Flags

`service deprecate` / `service version deprecate`

Flag	What it does	Example
`--at`	Effective date, `YYYY-MM-DD`	`fused-cli service deprecate stripe --at 2026-12-01`
`--reason`	Why, for the people who will read the notification	`fused-cli service deprecate stripe --at 2026-12-01 --reason "Provider EOL"`

`service remove` / `service version remove`

Flag	What it does	Example
`--force`	Removes it despite SDK or MCP configs that still reference it	`fused-cli service version remove stripe 2024-04-10 --force`

`service operation list`

Flag	What it does	Example
`--search`	Searches operations server-side	`fused-cli service operation list stripe --search refund`
`--version`	Pins the lookup to one enabled version	`fused-cli service operation list stripe --version 2024-06-20`
`--limit`	Rows to read	`fused-cli service operation list stripe --search refund --limit 50`
`--offset`	Rows to skip	`fused-cli service operation list stripe --search refund --offset 50`

Check what a version actually offers

Before you point an app at a new version, confirm the operations you depend on still exist under it.

fused-cli service operation show --registry <service-slug> <operation-name>

fused-cli service version list --registry stripe
fused-cli service operation list stripe --version 2024-06-20 --search refund
fused-cli service operation show --registry stripe createRefund --version 2024-06-20

Request and response contracts are opt-in on service operation show --registry — add --include-request or --include-responses — so a large schema does not arrive unless you asked for it.

Ship a new SDK version

Once a new service version is enabled, publish an SDK version that uses it.

Get Started

Guides

Advanced

Reference

Manage versions and deprecation

Run more than one version

Announce a deprecation

Remove it for real

Flags

`service deprecate` / `service version deprecate`

`service remove` / `service version remove`

`service operation list`

Check what a version actually offers

Ship a new SDK version

​Run more than one version

​Announce a deprecation

​Remove it for real

​Flags

​service deprecate / service version deprecate

​service remove / service version remove

​service operation list

​Check what a version actually offers

Ship a new SDK version

Run more than one version

Announce a deprecation

Remove it for real

Flags

`service deprecate` / `service version deprecate`

`service remove` / `service version remove`

`service operation list`

Check what a version actually offers