Skip to content

No API versioning (/v1) — breaking changes have no migration path #121

Description

@Darkdruce

Summary

Routes are unversioned (/payments, /merchants), so any breaking change affects all clients at once.

Location

  • src/api/mod.rs:50-82

Details & impact

A payment API needs a stable contract; without versioning there's no way to evolve request/response shapes without breaking integrators.

Suggested fix

Introduce a /v1 prefix and a documented deprecation policy.

Acceptance criteria

  • Public routes are versioned.

Metadata

Metadata

Assignees

No one assigned

    Labels

    GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26apiHTTP API surface and handlersdocumentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions