fix: Start config.toml lookup in tauri dir, not workspace root

.changes/targetdir-lookup-workspace.md

@@ -0,0 +1,5 @@
+---
+action: patch
+---
+
+Fixed an issue that caused `tauri-action` to not detect `build.target` in `.cargo/config.toml` if the app was part of a cargo workspace.

src/build.ts

@@ -75,10 +75,10 @@ export async function buildProject(
       .toLowerCase();
   }
 
-  const cratePath = getWorkspaceDir(app.tauriPath) ?? app.tauriPath;
+  const workspacePath = getWorkspaceDir(app.tauriPath) ?? app.tauriPath;
 
   const artifactsPath = join(
-    getTargetDir(cratePath, !!targetPath),
+    getTargetDir(workspacePath, info.tauriPath, !!targetPath),
     targetPath ?? '',
     profile ? profile : debug ? 'debug' : 'release',
   );

src/utils.ts

@@ -116,12 +116,16 @@ export function getWorkspaceDir(dir: string): string | null {
   return null;
 }
 
-export function getTargetDir(crateDir: string, targetArgSet: boolean): string {
+export function getTargetDir(
+  workspacePath: string,
+  tauriPath: string,
+  targetArgSet: boolean,
+): string {
   // The default path if no configs are set.
-  const def = join(crateDir, 'target');
+  const def = join(workspacePath, 'target');
 
   // This will hold the path of current iteration
-  let dir = crateDir;
+  let dir = tauriPath;
 
   // hold on to target-dir cargo config while we search for build.target
   let targetDir;