[karhu]

The Stack

This stack covers refactoring the internal logic of how releases are resolved during read, download & build, in particular also in the context of parent releases / parent datasets. On top of that it refactors the public TimeNet APIs and CLI interfaces around these actions, to streamline the behavior across them.

This PR

Renames ParentStep to Step, so that the parent planner and the coordinator use the same step type.

Details

This PR is mostly a cleanup. The parent planner already works with ParentStep objects, and the coordinator will use steps as well. This PR consolidates the two.

• ParentStep becomes Step(release, action, depends_on, pinned_by).
• The action "fetch" becomes "copy", the word that the copy function and the progress events use.
• depends_on lists the releases of the plan that must be in place before the step runs. A dependency that the output already holds has no step, so it is not listed.

Design decisions

• The list of steps is a graph, not a tree. A parent that two releases share appears once, and depends_on names every release that needs it.
• Step gets more fields later in the stack (the entry that provides a release, a force flag, and a "read" action). All are additions.

Breaking changes

• None.

Stack

• docs: update the docs for the build coordinator #683
• feat(hints)!: give every error one hint for the SDK and one for the CLI #698
• feat(cache)!: record where each release in the local registry comes from #674
• feat(client)!: list and search every source #673
• feat(client)!: replace get() with get_manifest() and get_card() #672
• feat(build)!: build into the local registry, publish with --publish-to #671
• feat!: add timenet.build() and publish() #670
• feat(cli)!: take --local-registry, --remote-registry and --auto-build #669
• feat(config)!: make the default list of sources from three variables #668
• test: isolate every test from the real home and guard it #667
• feat(client)!: download releases into the local registry #662
• feat(client)!: take an ordered list of sources #661
• feat(client)!: read releases through the coordinator #660
• feat(coordinator)!: plan and run reads through the list of sources #659
• feat(coordinator)!: plan parents through an ordered list of sources #658
• feat(sources)!: resolve a release through an ordered list of sources #657
• feat(build)!: run every build through the coordinator #655
• feat(build)!: move the build CLI and build() onto the coordinator #654
• feat(build)!: build one prepared release in the built-in backend #653
• feat(coordinator)!: plan and run builds through build_release #652
• 👉 refactor(coordinator)!: name the plan step type Step #651
• feat(registry)!: copy a release between registries #649
• feat(registry)!: publish a local release with put_release #648
• refactor(build)!: let the connector choose the values backend #646

Changes later in the stack: nothing in this PR.

Merge message

refactor(coordinator)!: name the plan step type Step

The parent planner returns Step objects with explicit dependencies, so
that the coordinator can use the same step type.

- depends_on lists the releases of the plan that must be in place
  first. A release that two others need appears once, so the steps
  form a graph.
- The action "fetch" becomes "copy", the word of the copy and its
  progress events.
- A ruff rule refuses imports of timenet_connectors in the timenet
  package, so that the SDK works without the connector package.

BREAKING CHANGE: ParentStep becomes Step, its reference field becomes
release, and its "fetch" action becomes "copy".

BREAKING CHANGE: depends_on is the new third field of a step, so
pinned_by moves to the fourth position.

[github-actions]

✅ CI checks passed

Check	Status
Quick checks	✅ Passed
Tests (Python 3.13)	✅ Passed
Tests (Python 3.11)	✅ Passed

_{Updated for 32ee397 · run #8351}

[TimoStoff]

The action is now "copy", but the module still says "fetch" everywhere else: the fetch_from parameter, the fetched set on the graph, and a ton of docstrings that say "the plan fetches". fetch_from is also the CLI flag. Should we make that naming consistent?

[TimoStoff]

LGTM! With some nits

[RealLast]

As discussed, accepting to unblock : ) We can clean up later

[claude]

Code review completed

Nothing new to post: everything this review found is already covered by existing comments on this pull request or didn't merit a separate one.

[claude]

Code review completed

Nothing new to post: everything this review found is already covered by existing comments on this pull request or didn't merit a separate one.

[claude]

Code review completed

Nothing new to post: everything this review found is already covered by existing comments on this pull request or didn't merit a separate one.