Skip to content

Deprecate Maestro 1.39.1 and 2.4.0#2

Merged
finalerock44 merged 1 commit into
devfrom
feat/maestro-deprecate-1.39.1-2.4.0
May 29, 2026
Merged

Deprecate Maestro 1.39.1 and 2.4.0#2
finalerock44 merged 1 commit into
devfrom
feat/maestro-deprecate-1.39.1-2.4.0

Conversation

@finalerock44

Copy link
Copy Markdown
Contributor

Summary

  • Adds 1.39.1 and 2.4.0 to REMOVED_MAESTRO_VERSIONS in src/commands/cloud.ts so the CLI hard-errors locally before reaching the API, matching the dcd compatibility.service.ts change.
  • Drops the stale 1.39.1 entry from the JSDoc example in src/types/schema.types.ts and src/types/generated/schema.types.ts to keep them aligned with the live dcd swagger.

No DEPRECATED_MAESTRO_VERSIONS block exists here (only the legacy dcd CLI had one) — nothing to delete.

Validation

  • pnpm lint — 0 errors (pre-existing warnings only)
  • pnpm build — clean

Test plan

  • pnpm dcd cloud ... --maestro-version 1.39.1 against any backend — expect CliError before any network call

Context

Pairs with moropo-com/dcd#<pending>, moropo-com/infra#<pending>, devicecloud-dev/docs#<pending>, and moropo-com/back-office#<pending>. Active CLI isn't shipping yet — landing this so it's ready when the cutover happens.

Add both to REMOVED_MAESTRO_VERSIONS so the CLI hard-errors locally,
matching the dcd API gate. JSDoc example in the generated schema types
also pruned to keep the dev-server example aligned with reality.
@finalerock44 finalerock44 merged commit eabe70f into dev May 29, 2026
1 check passed
@finalerock44 finalerock44 deleted the feat/maestro-deprecate-1.39.1-2.4.0 branch May 29, 2026 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant