Skip to content

fix: show bundled workflows an upgrade has not copied - #69

Merged
harsha09 merged 1 commit into
mainfrom
fix/issue-36-bundled-workflows
Oct 23, 2026
Merged

harsha09 merged 1 commit into
mainfrom
fix/issue-36-bundled-workflows

Conversation

@harsha09

Copy link
Copy Markdown
Owner

Summary

Fixes #36. An upgraded CLI no longer hides bundled workflows that the project has not copied, and sdd init --force can refresh a file that still matches the bundle even when .sdd/.generated.json has no hash for it.

  • sdd workflows still lists the project workflows. It adds Not copied yet: … when this CLI ships packs that are not in .sdd/workflows/.
  • sdd new -w <name> still refuses a name that is not in the project. When the CLI ships that name, the error tells you to run sdd init --here --force.
  • A workflow or template with no manifest hash is recorded as generated when its bytes match the bundled file. A later --force can refresh it. A file that differs stays kept and gets no hash.
  • Non-interactive sdd init without --force still does not copy workflows or rewrite config.

Test plan

An older project only listed workflows already on disk, and init --force
would not record a file that matched the bundle when the manifest had no
hash. sdd workflows now names the missing packs, and a matching unmarked
file is recorded so a later --force can refresh it.
@harsha09
harsha09 merged commit 0ba8de5 into main Oct 23, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgraded CLI hides new bundled workflows until a forced re-init

1 participant