Skip to content

Add API versioning #18

@Rulexec

Description

@Rulexec

Looks like issue for version 1.0.0, but we need to prepare for it and use versions to be able to change API in the future.

For HTTP API I propose just prefix all paths with version /v0/, /v1/.

Minor/patch versions are not required since we should not break anything and from v1 only add new methods/optional fields.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions