Skip to main content

Publish a library version

POST 
/api/publish_library_version

Snapshots the library's current working copy into an immutable libraries/.versions/<name>/<version>/ folder and bumps the working copy's library.json to that version.

A version is immutable, and every node that pins one relies on that, so the check that it is not already taken has to hold across all of the project's collaborators - not just the caller's own clone.

It must also move forward. Uniqueness alone would allow 1.0.4 after 2.0.0, which leaves the version list no longer describing the order the code was written in - and that order is the whole basis on which a node is told it is behind (the Scripting page's update dot, and the catalog upgrade list, both compare version numbers, not publish dates).

Request​

Responses​

Successful Response