Fetch, lock, update

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Standard.

Manifests declare intent. Locks declare what actually happened, so CI and your laptop stop arguing.

The trio

Command	Role
fetch	Resolve and materialize dependencies into obj/beskid
lock	Synchronize Project.lock with current resolution
update	Refresh resolution and materialized tree when policy allows

Reference: fetch, lock, update, lockfile guide.

Frozen / locked builds

CI should prefer reproducible resolution:

• --frozen: fail if lock would change
• --locked: enforce lock consistency (see per-command docs for exact semantics)

sequenceDiagram
  accTitle: Project dependency resolution
  accDescr: The fetch and lock commands read the bproj manifest through the resolver, materialize dependencies under obj/beskid and sync Project.lock, and frozen CI fails if the lock would change.
  participant You
  participant CLI as beskid CLI
  participant Res as Resolver
  participant Lock as Project.lock
  participant Obj as obj/beskid
  participant CI as CI with --frozen
  You->>CLI: fetch
  CLI->>Res: Resolve App.bproj
  Res->>Obj: Materialize dependencies
  You->>CLI: lock
  CLI->>Res: Resolve App.bproj
  Res->>Lock: Synchronize with current resolution
  CI->>Lock: Read recorded state
  Lock-->>CI: Fail if the lock would change

Text equivalent: fetch resolves App.bproj and materializes dependencies under obj/beskid. lock synchronizes Project.lock with the current resolution. CI runs with --frozen and fails if the lock would change.

When the lock changes

Expect Project.lock updates when:

• You add/remove/retarget dependencies
• Path dependencies move on disk (sometimes)
• Resolver policy or toolchain version changes resolution

Do not .gitignore the lock because “it is generated” unless you enjoy production roulette.

Path-only era (v1)

With source = path, drift can mean different local folders. With source = registry, inspect the selected active version in Project.lock. Workspaces add shared override policy: chapter 06.

Standard reference (informative)

• Workspace and lock contracts

Next

Tree and resolution