cc @DanTup

PR Health

// Copyright (c) 2025, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

Package publishing

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

Weird, I cannot replicate the originally reported error without this patch - the integration test I added at the end works either way.

Ahhh, so I can replicate this error with runInShell: true.

@jakemac53 for my original issue, the folder was named "Latest (Bleeding Edge)" which contains both spaces and quotes, so I would've expected it to already be quoted (in fact in the screenshot, it looks wrapped in quotes). Might there be more to it?

I can do some testing locally tomorrow and see if I can confirm if this fixes it (and if not, try to figure out why).

Oh, this sounded familiar and I found this in Dart-Code:

	// Spawning processes on Windows with funny symbols in the path requires quoting. However if you quote an
	// executable with a space in its path and an argument also has a space, you have to then quote _all_ of the
	// arguments!
	// https://github.com/nodejs/node/issues/7367

https://github.com/Dart-Code/Dart-Code/blob/7f51d4c35f48b0bb69f7913aaa94e6b501e403f4/src/shared/processes.ts#L30-L33

Shell execute is a mess. If you know you're getting dart.exe (and not the dart shell script from Flutter's bin folder), I wonder if you should skip shell execute instead? In Dart-Code we now only use the shell if the target ends with .bat:

https://github.com/Dart-Code/Dart-Code/blob/7f51d4c35f48b0bb69f7913aaa94e6b501e403f4/src/shared/processes.ts#L19

When testing locally on windows it seems like the dart issue has since been closed and now this helper code is actually causing problems when parentheses are involved.

I have now removed the helper and its tests, and added integration tests that actually run an executable, and also added windows testing to the GitHub workflows for this package.

Ok, so actually it looks like when there are only parenthesis this still doesn't work. However, simply wrapping it in quotes also doesn't work.

I don't know what the right thing to do here is.

Shell execute is a mess. If you know you're getting dart.exe (and not the dart shell script from Flutter's bin folder), I wonder if you should skip shell execute instead? In Dart-Code we now only use the shell if the target ends with .bat:

I can try this, but dang does that sound hacky lol.

Shell execute is a mess. If you know you're getting dart.exe (and not the dart shell script from Flutter's bin folder), I wonder if you should skip shell execute instead? In Dart-Code we now only use the shell if the target ends with .bat:

I can try this, but dang does that sound hacky lol.

Perhaps, but escape correctly for shell is already a minefield (see dart-lang/sdk#59604 for some issues that were never resolved). If you know you're executing a binary and don't need the shell, avoiding it makes things simpler.

I'll see if I can pull these changes in locally and test my original problem and post back.

I restarted the windows jobs to see if they get picked up... if not I guess I will remove them as they don't ever seem to run 😭

Looks like it was just a bad OS name and GitHub likes to waste time queueing jobs for oses that don't exist :P

Btw I skipped the test for having just parenthesis in the path and filed a separate issue. This is not a regression, its a new test that is failing (there was no special handling for this case before).