[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

timenet-build build always builds into the store, takes its parents from the default list of sources, and publishes with --publish-to. It prints its plan first and stops after the plan with --dry-run.

Details

timenet-build build had its own flags for where a build lands and where its parents come from: --out, --fetch-from and --build-parents. The other entry points take the default list of sources instead. So the same build needs other inputs on the command line than in Python.

• The build lands in the store. Missing parents and payload sources come from the default list: the remote registry, then the installed connectors. --local-registry, --remote-registry and --auto-build/--no-auto-build set that list for one command. The connector of the requested dataset builds it also with --no-auto-build.
• --publish-to URL publishes the release after the build with timenet.publish(), and the command prints the version.
• The command plans with plan_release_build() of the coordinator, runs the plan, and prints the release directory.
• The plan goes to stderr before the first step, as a tree. The requested release is at the top, and below each release are the releases that it needs. Each line names the release, the action and the source. --quiet hides the plan.
• --dry-run prints the tree to stdout and stops. It copies, builds and publishes nothing, and it makes no store directory.
• The hints name the new flags. A damaged copy points to timenet download or a forced rebuild. If the command got --local-registry or --remote-registry, the hint repeats them.
• The example uses the new flags.
• Size: about 830 changed lines. The new flags, the plan output and --dry-run share one code path in the command, so they read best together.

Design decisions

• The command prints the plan that it then runs, so the printed plan and the run cannot differ.
• A test makes sure that --dry-run prints the exact plan and copies, builds and publishes nothing.
• The plan goes to stderr and the dry run to stdout. A script can read the dry run, and a normal run keeps stdout for the release directory.
• The command reads the default list before it opens --publish-to. A registry reads the settings when it opens. Otherwise an invalid variable shows as an invalid value of --publish-to.
• The destination is not a source of parents, because a published release is a result and not an input.
• If the destination holds the version, nothing runs. With --force, the release builds again in the store only, and the publish copies nothing for the same release. The publish refuses other files or another card.
• A destination that is not local makes the plan refuse a release that is not open, before any download.
• An empty --publish-to, or one that names no registry, raises TimeNetRegistryError before any build. It never means the current directory.

Breaking changes

• timenet-build build drops --out, --fetch-from and --build-parents.
• Every build lands in the store.
• Missing parents come from the default list: the remote registry, then the installed connectors.
• The destination of --publish-to is no source of parents.
• --force with a --publish-to that holds the version rebuilds into the store, and the publish refuses other files.

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:

• docs: update the docs for the build coordinator #683 holds the doc changes of this PR.

Merge message

feat(build)!: build into the local registry, publish with --publish-to

timenet-build build always builds into the local registry and takes
its parents from the default list of sources, as the Python API does.
It publishes with --publish-to.

- --local-registry, --remote-registry and --auto-build/--no-auto-build
  set the list for one command. The connector of the requested dataset
  builds it also with --no-auto-build.
- The command prints the plan that it runs as a tree on stderr before
  the first step. --dry-run prints the tree on stdout and stops.
- If the destination already holds the version, nothing runs unless
  --force is set. A destination that requires open access makes the
  plan refuse other releases before any download.
- The destination is no source of parents, because a published
  release is a result.

BREAKING CHANGE: timenet-build build loses --out, --fetch-from and
--build-parents. Every build lands in the local registry, and missing
parents come from the remote registry, then the installed connectors.

[TimoStoff]

OK ....thats it for today I think 😓

[claude]

Code review found no issues

No high-confidence issues detected in this change.

[claude]

1 optional suggestion (a nit or a note on pre-existing code) was found and not posted.

[claude]

Code review found no new issues

No new issues were found in this update; 1 finding from earlier reviews is still open above.

1 optional suggestion (a nit or a note on pre-existing code) was found and not posted.

Still open from earlier reviews (1):

• 🔴 packages/timenet-connectors/src/timenet_connectors/builder/cli.py:131 — Publishing a child dataset to a private registry that already holds its parent can now rebuild that parent locally. The…

If you have decided not to act on one of these findings, resolve its thread (a reply alone leaves it open) and the next review stops counting it. To review this commit again now, use Re-run on its "Claude Code Review" check.