Implement API versioning for deployment endpoints using ApiVersionRouter

[temma02]

Description

ApiVersionRouter is tested in apps/backend/tests/api/versioning.test.ts but not wired into any route. Deployment endpoints should be versioned so breaking changes can be introduced without disrupting existing SDK consumers.

Requirements and context

• Must be secure, tested, and documented where applicable
• Should stay reviewable and fit the current monorepo structure
• Relevant files: apps/backend/tests/api/versioning.test.ts, apps/backend/src/app/api/deployments/route.ts, packages/sdk/src/client.ts

Suggested execution

• Create branch: issue-016-api-versioning-deployment-endpoints
• Keep changes scoped to the issue and reference the task IDs in the PR

Implement changes

• Register v1 handlers for GET /api/deployments and POST /api/deployments via ApiVersionRouter
• Read the version from the API-Version request header; default to v1
• Return Deprecation response header when a non-current version is requested

Test and commit

• Add route tests for version header negotiation and deprecation header presence
• Update CraftClient in the SDK to send API-Version: v1 on all requests
• Edge case: unknown version — return 400 with supported versions list

Example commit message

feat(api): add versioning to deployment endpoints

Guidelines

• Prefer small, reviewable PRs
• Keep naming and data contracts consistent with the spec docs

[Malcolm-Wander]

@Malcolm-Wander has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hello maintainer, I’d love to work on this issue,I have experience designing scalable backend architectures and managing backward-compatible API evolution.
I can implement API versioning for deployment endpoints using an ApiVersionRouter with clear routing and deprecation strategy.
My approach ensures safe iteration, smooth client upgrades, and long-term maintainability of the API.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Malcolm-Wander to this issue.

[drips-wave]

Congratulations, @Malcolm-Wander! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Malcolm-Wander: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊