strategies

Upgrade Strategy Lock

Bump the NON-breaking pins and save them — a thin wrapper over PATCH.

Spec 02 (Contract): of the requested drifting pins (all when components is omitted), only those whose bump alone keeps the strategy valid are moved; breaking ones (an interface change, a deprecation, an unknown component) are listed in skipped_breaking for a recomposition. The bumped lock is saved through PATCH (lock-only) and only when it validates: an invalid combination writes nothing. The caller names the version it read — expected_head_commit_id, or both content hashes — and a moved HEAD is a 409 before anything is computed.

post/v1/strategies/{strategy_id}/lock/upgrade

Request

  • Base URL: https://api.usekeel.io (the document declares no server; this is the origin it was published from)
  • URL: https://api.usekeel.io/v1/strategies/{strategy_id}/lock/upgrade
  • Auth: none declared

Path parameters

strategy_idstring required

Headers

Authorizationstring nullable
X-Org-Idstring nullable

Request body

componentsstring[] nullable
expected_head_commit_idstring nullable
expected_source_hashstring nullable
expected_lock_hashstring nullable

Response

Successful Response

upgradedobject[] required
component_lockobject required
lock_hashstring required
validboolean nullable
issuesobject[]
messagestring nullable
persistedboolean
skipped_breakingstring[]

Changes

No recorded changes to this operation across all 2 revisions of this API.