You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
squad upgrade installs Squad's own CI/release workflows that init deliberately skips (regression of #201) #2527
Version: CLI built from release/prepare-2.0.0-preview.5 @ 38d45d02 (package version 2.0.0-preview.6).
What happens
squad init installs only the four framework workflows (#201). Running squad upgrade right after, with nothing changed in between, adds seven more workflows. These are Squad's own product CI/CD, built for Squad's dev/preview/main/insider branch model.
A real squad upgrade creates all seven files. For a non-npm project, the five in PROJECT_TYPE_SENSITIVE_WORKFLOWS become TODO stubs that still trigger on pushes and PRs to dev/preview/main/insider. squad-promote.yml and squad-label-enforce.yml are copied verbatim.
Expected
upgrade installs and refreshes the same workflow set that init installs (FRAMEWORK_WORKFLOWS). It updates any other squad-*.yml only if it's already present, because the user opted in. It never creates one.
packages/squad-cli/src/cli/core/upgrade.ts, collectSquadOwnedCandidates (line 606). Line 623 onward iterates every*.yml in templates/workflows/ and plans each as a candidate, with no FRAMEWORK_WORKFLOWS filter.
packages/squad-cli/src/cli/core/templates.ts, lines ~350–415: TEMPLATE_MANIFEST lists all 11 workflows with overwriteOnUpgrade: true.
packages/squad-cli/src/cli/core/workflows.ts, line 8: PROJECT_TYPE_SENSITIVE_WORKFLOWS.
Activity