jschoubben 38a2492394 RN3 (publish half): a pipeline starts by compare-and-set on its key, and a package-published starts one per dependent behind ...

A start writes the pipeline's key (watched branch, source revision, module) only when it is absent and says
pipeline-started; a second start of the same revision and module writes nothing. A package-published asks the
catalog's outdated for that package on that branch, a kept call, and starts a pipeline for each dependent behind
by kind 1, keyed by the publication's branch and source revision. The start on take-in.taken, and a gathered
group's one pipeline per branch, wait for take-in.taken's body (design 47 G §476, in review).

Builds: design 47 G §54, §103, §334, §53, §75

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

2026-11-11 12:34:26 +01:00

..

cmd

RN3 (publish half): a pipeline starts by compare-and-set on its key, and a package-published starts one per dependent behind

2026-11-11 12:34:26 +01:00

internal/pipeline

RN3 (publish half): a pipeline starts by compare-and-set on its key, and a package-published starts one per dependent behind

2026-11-11 12:34:26 +01:00

go.mod

RN3 (publish half): a pipeline starts by compare-and-set on its key, and a package-published starts one per dependent behind

2026-11-11 12:34:26 +01:00

go.sum

RN1: the pipeline runner's module, a foundation part with its kept data in old sections (issue 1966)

2026-11-11 11:32:31 +01:00

manifest_test.go

RN3 (publish half): a pipeline starts by compare-and-set on its key, and a package-published starts one per dependent behind

2026-11-11 12:34:26 +01:00

module.json

RN3 (publish half): a pipeline starts by compare-and-set on its key, and a package-published starts one per dependent behind

2026-11-11 12:34:26 +01:00