Skip to main content

Move chosen nodes onto a newer version of a catalog's library

POST 
/api/update_library_dependents

Rewrites each named node's copy of a library and re-pins it, in one commit.

Names a catalog to move onto a version that catalog publishes, installing it into the project on the way; omits it to move onto a version of the project's own library, which publishing has already snapshotted. Nothing else differs - a node cannot tell where the files it holds came from.

Nodes the runtime has active are skipped rather than refused: the batch exists to move twenty nodes at once, and one node someone happened to start should not cost the other nineteen their update. The same is true of a node that has since been unlinked from the library or is already on the target version - every one comes back in skipped, with a reason, so the caller can tell "nothing to do" from "not done".

A node following a catalog adapter is skipped too, and that one is a genuine redirection rather than a hiccup: its library pins are part of the adapter release it claims to follow, so moving one underneath it would leave the node disagreeing with its own origin. Those are updated by updating the node from its catalog (update_node_from_template).

Request​

Responses​

Successful Response