Skip to content

Saving new version of a published API? #18

@dahlsailrunner

Description

@dahlsailrunner

I have a published API that had a version attribute of '1'. When I went to save a new version of the API (v '1.0.1') it gave an error saying that I couldn't save changes to a published API.

When I "unpublished" the v1 API, then I could save the 1.0.1 version and it saved a new version of the API, and then I had to go back and re-publish the original v1 version.

Is this the intended functionality / workflow here? I expected that me saving 1.0.1 from a published version would have created a new unpublished version and left the published one alone.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions