Yazeed Obaid

Thanks for reporting. Can you please use the create process API instead? Since the `asyncShellExex` is marked with an obsolete attribute. https://github.com/fsprojects/FAKE/blob/79aa1273d0311595bd404be5721d994301774552/src/app/Fake.Core.Process/Process.fs#L826-L829

Thanks for reporting. The `ReleaseNotes` module in FAKE follows guidelines in [keepachangelog](https://keepachangelog.com/en/1.1.0/) site. And changelog files should be ordered in chronological order based on the version, in which entries are...

closing this due to inactivity, please feel free to re-open or open a new issue if anything still needs to be addressed.

@knocte yes I approved the CI run. For first-time contributors, the CI needs admin approval. Yes, it is not from your PR. It started to happen randomly after the last...

Hi thanks for the PR Could you please rebase your branch from `release/next`? Now that the build has been fixed.

Thanks for the fix, can u please try to add tests to it?

Log with nestandard2.0 framework restriction in paket.dependencies ``` dotnet fake -vv build runOrBuild ({ Script = None ScriptArguments = [] FsiArgLine = [] Debug = false NoCache = false RestoreOnlyGroup...

It should not be a breaking change (please correct me if I'm wrong) since Net 6 is backward compatible with Netstandard2.0, so it should resolve the packages. But maybe we...

Sorry for the hassle, it was unintended and a case that we didn't cover

Thanks for reporting! Would anyone like to send a PR for this issue?