spl:outdated

Report products pinned to an older SPL model than the one that exists.

Usage

splent spl:outdated [--remote]

Requires detached mode. It reads every product in the workspace.

Options

Option	Description
`--remote`	Also ask UVLHub whether the line itself has moved on. Needs a concept DOI.

Description

Pinning a model by DOI makes a build reproducible, which also means a product sits on the version it was pinned to forever and never says so. This is the command that says so.

Two questions, and they are not the same one.

Local drift. The workspace already holds a newer model than the product pins, because someone published from the working copy here. No network.
Remote drift. The line itself has moved on somewhere else. That needs the concept_doi recorded by spl:pin, which is exactly why it is recorded.

Without --remote the command consults only this workspace, and says so in its summary.

Example

splent spl:outdated

  spl:outdated

  cms_spl
    innosoft_app            pins v2, this workspace holds v3
    diversolab_app          pins v3, up to date

  2 product(s) checked, 1 behind
  Only this workspace was consulted. Add --remote to ask UVLHub.

Move one forward with spl:pin.

It never reports “up to date” on a guess

A concept DOI resolves to a landing page whose machine readable shape is not part of any contract the CLI controls. So a shape it does not recognise, and a product with no concept DOI recorded, are both reported as “could not be determined” and counted separately from the ones that are in sync. A product with no DOI at all is reported as needing spl:pin.

An unreachable UVLHub, or a non-200 answer, fails the command outright rather than being read as “nothing has changed”.