fix(cli): a `--global` rebuild for a newer release keeps the files that release removed

Ouverte
#1,230 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
typescript
Domaine
build-system, cli

Piste de recherche

Start in cli/src/contexts/framework/application/shared/ensure-built-marketplace-use-case.ts: compare the stale-sentinel path that reaches runBuild with buildViaTemp, which already clears the built directory first. Check open PR #1145, which proposes the same deleteDirectory fix, before starting. Done when a --global upgrade from v5.13.0 to v5.14.0 leaves the built folder with the same file count as a clean v5.14.0 install (540 files).

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Description

The built framework lives at ~/.config/aidd/cache/built/<cli version>/ (the path carries the CLI version, not the framework release). When the same CLI moves a --global install to a newer release, the build is written over the previous one, and the files the new release removed stay. Claude Code still lists the skills and agents among them.

Cause: in ensure-built-marketplace-use-case.ts, when the sentinel is stale (l.126-129), build reaches runBuild (l.176-188), which writes into builtDir without clearing it. buildViaTemp clears it first (l.168).

Open PR #1145 already adds deleteDirectory(builtDir) before the build ("a new build must not inherit deleted files"). This issue gives it a reproduction and a measured scope.

Affected file(s)

cli/src/contexts/framework/application/shared/ensure-built-marketplace-use-case.ts

Expected behaviour

After moving to v5.14.0, the built folder holds exactly the files of a clean v5.14.0 build.

Observed behaviour

In an empty HOME (XDG_CONFIG_HOME=$HOME/.config, AIDD_USER_CONFIG_DIR=$HOME/.config/aidd, CLAUDE_CONFIG_DIR=$HOME/.claude, AIDD_SKIP_UPDATE_CHECK=1), with aidd 5.7.0:

aidd setup --global --source remote --release v5.13.0 --ide claude \
  --plugins aidd-context,aidd-dev,aidd-orchestrator,aidd-pm,aidd-refine,aidd-vcs --yes
aidd setup --global --source remote --release v5.14.0 --ide claude \
  --plugins aidd-context,aidd-dev,aidd-orchestrator,aidd-pm,aidd-refine,aidd-vcs --yes

Compared with a clean v5.14.0 install in another empty HOME:

  • 603 files against 540: 63 files survive, in 4 plugins (aidd-context 40, aidd-dev 13, aidd-refine 8, aidd-ui 2).
  • claude plugin details aidd-dev@aidd-framework: Agents (2) checker, executor, against Agents (0) on the clean install.
  • claude plugin details aidd-refine@aidd-framework: 6 skills, with 05-improve beside 05-review-conversation (renamed by #1068), against 5 on the clean install.
  • Whole removed skills that survive: aidd-refine/05-improve, aidd-ui/01-hello. Also aidd-context/hooks/update_memory.js.
  • aidd sync --global --force rebuilds without removing them.
  • aidd doctor --global: "User-scope installation is healthy".
AI tool

Claude Code

aidd-cli version

5.7.0

OS

Linux

Additional context

Claude Code 2.1.325. The v5.14.0 tag holds no 05-improve, and there is no symlink under ~/.config/aidd/cache/built.

Code of Conduct
Langage dominant
TypeScript
Étoiles
481
Forks
45
Merge moyen
1 j 13 h
PR mergées (30 j)
91

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ai-driven-dev/framework

Toutes les issues de ai-driven-dev/framework

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.