[sentry-junior]

Fixes #953.

craft prepare --dry-run with automatic version bumping wrote the bump into the user's checkout, not the temporary worktree. So the next dry run computed a higher version.

The cause: findConfigFile() cached the original checkout's .craft.yml path from before isolation. After the dry run moved into the worktree, getReleaseUnitDir() still resolved to the original checkout, and npm version ran there. Worktree mode allowed it.

Changes:

• findConfigFile() now caches per working directory, so the config path is found again after the dry run moves into or out of the worktree.
• createDryRunIsolation() now moves into the worktree directory that matches the original working directory, not the worktree root. Without this, a .craft.yml in a subdirectory would not be found once the cache stops hiding the mismatch. Dependency symlinks go to the same place.
• Cleanup deletes local branches the dry run created. The worktree shares refs with the checkout, so release/<version> stayed behind. Once both runs compute the same version, the second dry run would fail with "Branch already exists".

The new e2e test runs an automatic npm workspace bump twice. It checks that both runs compute the same version, that package.json and git status stay unchanged, and that no release branch is left. The existing worktree test now checks that the release branch is removed, where it used to note that the branch may stay. I checked both behaviors by hand with the built binary: workspace config and subdirectory config, run twice each. I could not run the e2e suite locally because a sandbox git hook rejects its test author identity, so CI is the first full run.

via @BYK.

--

View Session in Sentry

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0de3e53. Configure here.}