Pin Publish Fragment to deploy-kit 1.0.0 #197

Activity

1. ExtraToast

   added

   type: choreMaintenance work without intended behavior change.Maintenance work without intended behavior change.

   area: deployhomelab-deploy, deploy-v2, manifests, and rollout flow.homelab-deploy, deploy-v2, manifests, and rollout flow.

   priority: P1High; important and should be handled in the current iteration.High; important and should be handled in the current iteration.

   status: blockedCannot move forward until an external dependency is resolved.Cannot move forward until an external dependency is resolved.

   on Oct 27, 2026
2. ExtraToast

   added a parent issue on Oct 27, 2026

   • Republish delivery, _canary and _estate on 1.0.0 deploy-kit#380
3. ExtraToast

   added

   status: in-progressActively being worked.Actively being worked.

   and removed

   status: blockedCannot move forward until an external dependency is resolved.Cannot move forward until an external dependency is resolved.

   on Oct 27, 2026
4. ExtraToast commented on Oct 27, 2026

   

   ExtraToast

   on Oct 27, 2026

   Last edited by ExtraToast

   ContributorAuthor

   More actions

   Resume here (updated 2026-10-27)

   State: done. PR #199 merged, and v0.36.0 is released (16d241e4). Its tools/deploy-kit pins 1.0.0, read back at the tag.

   Next step: read one fragment published through it by digest (auth-api or n8n, step 3 of JorisJonkers-dev/deploy-kit#380) and confirm schemaVersion 1.0.0. That check is tracked on JorisJonkers-dev/deploy-kit#380.

   Gotchas: render-diff composes without --participants (#198).
5. ExtraToast

   added a commit that references this issue on Oct 27, 2026

   feat: publish fragments with deploy-kit 1.0.0 (#199)

   ...

   This issue will close once commit e05ad55 is merged into the 'main' branch.

   e05ad55
6. ExtraToast

   closed this as completedin #199on Oct 27, 2026
7. ExtraToast

   removed

   status: in-progressActively being worked.Actively being worked.

   on Oct 27, 2026