release: orchestration engine, forge confirmations, CI and module publishing #5

Merged
crapougnax merged 16 commits from develop into main 2026-11-07 23:00:50 +00:00
Member

Release of develop into main. Merge with a merge commit (GitFlow), not squash.

Content

  • #1 orchestration: targets from target.yaml, guided run (durable IPs → DNS stop → reverse DNS → cluster → kubeconfig and marker → stacks), Terraform roots from the catalogue modules, guards (saved plans, no destroy).
  • #2 orchestration: exact pool names, Scaleway key/project check, organisation-aware targets (org/name), pools start at their minimum, confirmations through the core (no --yes).
  • #3 forge: confirmation of every destructive command (pr merge, mirror sync, git force/delete/reset --hard…, gh/tea/glab delete/close…).
  • #4 CI on every push; publication of a module on @tycho/<module>@X.Y.Z tags.

After the merge

  1. Repository secret PACKAGES_TOKEN (write:package) must exist for the release workflow.
  2. Versions: @tycho/forge is 1.0.0; @tycho/orchestration is still 0.1.0 in its package.json: bump it in a PR on develop before tagging it (it requires core ^1.0.0, the core with ctx.target and ctx.confirm).
  3. Tags on main: @tycho/forge@1.0.0, then @tycho/orchestration@<version>.

🤖 Generated with Claude Code

Release of `develop` into `main`. **Merge with a merge commit** (GitFlow), not squash. ## Content - #1 `orchestration`: targets from `target.yaml`, guided run (durable IPs → DNS stop → reverse DNS → cluster → kubeconfig and marker → stacks), Terraform roots from the catalogue modules, guards (saved plans, no destroy). - #2 `orchestration`: exact pool names, Scaleway key/project check, organisation-aware targets (`org/name`), pools start at their minimum, confirmations through the core (no `--yes`). - #3 `forge`: confirmation of every destructive command (pr merge, mirror sync, git force/delete/reset --hard…, gh/tea/glab delete/close…). - #4 CI on every push; publication of a module on `@tycho/<module>@X.Y.Z` tags. ## After the merge 1. Repository secret `PACKAGES_TOKEN` (write:package) must exist for the release workflow. 2. Versions: `@tycho/forge` is 1.0.0; `@tycho/orchestration` is still **0.1.0** in its `package.json`: bump it in a PR on `develop` before tagging it (it requires core `^1.0.0`, the core with `ctx.target` and `ctx.confirm`). 3. Tags on `main`: `@tycho/forge@1.0.0`, then `@tycho/orchestration@<version>`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Replaces the shell placeholder with the engine of RFC-001 §3:
- target.yaml: types and fail-fast validation (every problem listed, no
  default for instance values, placeholders and branch refs refused);
- contexts: one tycho manages several targets (context add/use/list,
  --target, TYCHO_TARGET); one kubeconfig per target, 0600, outside the repo;
- catalogues fetched at a pinned ref; Terraform roots generated from the
  catalogue modules: durable public IPs and cluster, each in its own state;
- guided run: public IPs, stop until DNS records exist, reverse DNS, cluster,
  kubeconfig and ownership marker, stacks in requires order;
- guards: saved plans only, any destroy or replace refused, confirmation
  before each apply, cluster ownership checked before every kubectl change;
- stacks: ${VARIABLE} substitution limited to declared and built-in names,
  secrets only from SOPS.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Targets are now registered and selected by the Tycho core (tycho context,
--target, TYCHO_TARGET). The module acts on the target it receives and
refuses one whose engine is not kubernetes; it keeps only its local state
(kubeconfigs, catalogue cache). init prints the tycho context command.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- stacks are built with --enable-helm, by the standalone kustomize when
  installed (the kustomize embedded in kubectl calls `helm version -c`,
  removed in Helm 4), else by kubectl;
- tycho.modePath lets a recipe keep its variants elsewhere than
  <path>/overlays/<mode> (e.g. one directory per environment).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #1
Workloads may select nodes by the provider's pool name
(k8s.scaleway.com/pool-name); spec.cluster.pools.<key>.name sets it,
default unchanged (<cluster>-<key>-pool).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Before any plan, the description of the API key is read; a key whose
default project is not spec.projectId is refused. A scoped key that cannot
read its own description only warns: the per-target bucket policy of the
state is then the guard.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The module works on the target id org/name handed over by the core:
kubeconfig in kube/<org>/<name>.yaml, ownership marker and journal keyed by
the id; the repository must declare the selected name (and organisation
when it declares one). target.yaml accepts metadata.organization; init
asks it and prefixes the state key with it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A pool with min 0 (GPU, on demand) was created with one node; it now starts
empty and the autoscaler adds nodes when needed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each apply asks through the core's confirm(), which names the organisation
and target and refuses without a terminal unless TYCHO_ASSUME_YES=1. The
module's own --yes is removed: one way to confirm in CI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Asks before: pr merge, mirror sync, git commands passed through that lose
work or rewrite a remote (push --force/--delete/:ref/+ref/--mirror, reset
--hard, clean -f, branch -D/-d, stash drop|clear, tag -d, checkout -f,
restore, rm, gc --prune, reflog expire), and forge CLI passthrough that
deletes, closes, archives or transfers. Under the core, its confirmation is
used (it names the organisation and target); standalone, a terminal prompt.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ci: check every push, publish a module on @tycho/<module>@X.Y.Z tags
All checks were successful
CI / check (push) Successful in 25s
CI / check (pull_request) Successful in 30s
844ec0b001
- CI (push and pull request): typecheck, tests and build of every module
  (forge gets a typecheck script);
- Release (tag @tycho/<module>@X.Y.Z): the version must match the module's
  package.json, then typecheck, tests, build and npm publish to the registry
  of the tycho organisation on git.qtrn.io (served as qtrn.io/@tycho);
  secret PACKAGES_TOKEN (write:package).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-on: #2
Reviewed-on: #3
Merge branch 'develop' into ci/build-and-release
All checks were successful
CI / check (pull_request) Successful in 32s
CI / check (push) Successful in 32s
8f295172df
Merge pull request 'ci: check every push, publish a module on @tycho/<module>@X.Y.Z tags' (#4) from ci/build-and-release into develop
All checks were successful
CI / check (push) Successful in 26s
CI / check (pull_request) Successful in 30s
b7ba1eccf8
Reviewed-on: #4
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tycho/modules!5
No description provided.