[repo-assist] Monthly Activity 2026-09

[github-actions]

🤖 Repo Assist here — I'm an automated AI assistant for this repository.

Activity for September 2026

Suggested Actions for Maintainer

• Review PR [repo-assist] Fix: paket remove does not remove clitool packages from paket.dependencies #4405: Fix paket remove does not remove clitool packages from paket.dependencies — fixes Paket remove doesn't remove clitool packages from dependencies file #3654 — Review
• Review PR [repo-assist] Fall back to User/Machine scoped environment variables in paket.dependencies #4406: Fall back to User/Machine scoped environment variables in paket.dependencies — fixes paket.dependencies cannot resolve user level environment variables #3562 — Review
• Review PR [repo-assist] scriptgen integration tests fail due to unpinned NuGet versions in scenario fixtures #4399: scriptgen integration tests fail due to unpinned NuGet versions in scenario fixtures — Review
• Review PR [repo-assist] ci: disable broken scriptgen integration test job #4400: ci: disable broken scriptgen integration test job — Review
• Review PR [repo-assist] Flaky scriptgen integration test scenarios resolve against live NuGet feed (no committed paket.lock) #4401: Flaky scriptgen integration test scenarios resolve against live NuGet feed (no committed paket.lock) — Review
• Review PR [repo-assist] ci: derive SDK version for dotnet-install.sh from global.json #4411: ci: derive SDK version for dotnet-install.sh from global.json — Review
• Check comment Paket does not use global nuget cache directory set in configuration file #3853: Repo Assist confirmed the global NuGet packages folder issue was already fixed by commit 3e84a77; recommended closing — View
• Check comment dotnet tool paket clean cache issue #3781: Repo Assist root-caused clean-cache breaking local dotnet-tool installs and posted a workaround — View
• Check comment Paket show-installed-packages reports incorrect #3728: Repo Assist recommended closing as stale/needs-more-info (no repro since 2019) — View
• Check comment Could not detect any platforms from 'XCODE10' / 'XCODE11' #3816 / Could not detect any platforms warning #3703: Repo Assist root-caused spurious "Could not detect any platforms" warnings to the build/ TFM scanner in InstallModel.fs; proposed a fix direction pending maintainer sign-off — View
• Discuss: Pinned version in nuspec for .NET Core projects #3557 (pinned version lost in nuspec for SDK-style dotnet pack projects) — needs maintainer design sign-off before implementation.
• Decide: paket init should pin itself #3320 (paket init should pin its own version) — needs a maintainer decision before implementation.

Future Work for Repo Assist

• copy_local: true has no effect on netstandard projects #3810 (copy_local: true has no effect on netstandard projects): needs a concrete repro before a fix can be attempted.
• Paket.Core strict reference to Fsharp.Core  #4260 (Paket.Core's FSharp.Core dependency generated as = instead of >=): needs the exact SDK/PackageReference-driven code path located.
• Behavior differs from VisualStudio if bulid/xxx.targets and bulid/native/xxx.targets are present #4304 (native targets-file import mismatch): needs a design-level decision before a minimal fix path can be found.
• Continue working through the unlabelled-issue backlog (labelling cursor now past Paket does not use global nuget cache directory set in configuration file #3853).

Run History

2026-09-01 16:58 UTC — Run

• 🏷️ Labelled 30 previously-unlabelled issues from the backlog (Unable to set up paket with visual studio for mac on macOS #3594–Paket does not use global nuget cache directory set in configuration file #3853): mostly bug/enhancement/needs triage.
• 💬 Commented on Paket does not use global nuget cache directory set in configuration file #3853 (global NuGet packages folder ignored): confirmed already fixed by commit 3e84a77 which explicitly references this issue; recommended closing.
• Investigated copy_local: true has no effect on netstandard projects #3810 (copy_local: true has no effect on netstandard projects) but found no confident, low-risk fix path without a concrete repro; deferred.

Generated by 🌈 Repo Assist, see workflow run. Learn more.
_{Comment /repo-assist to run again}

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38

---

2026-09-01 (later run) — Run

• 🏷️ Labelled ~30 more previously-unlabelled issues from the backlog (Key not valid for use in specified state for windows containers #4170–Behavior differs from VisualStudio if bulid/xxx.targets and bulid/native/xxx.targets are present #4304, plus a few others in that range): mostly bug/enhancement/question/documentation. Hit the per-run 30-call labelling cap; a handful of issues in the Dependency manager looks up older tool version of paket #4164–Behavior differs from VisualStudio if bulid/xxx.targets and bulid/native/xxx.targets are present #4304 range are still unlabelled and will be picked up next run before advancing the cursor.
• 🔍 Investigated Invalid resolution on macOS for 'monoandroid10.0' #3820 (invalid resolution on macOS for monoandroid10.0) and Paket.Core strict reference to Fsharp.Core  #4260 (Paket.Core's own FSharp.Core dependency pinned with = instead of >=) as Task 3 candidates. Confirmed Paket's own NuGet package is built via dotnet pack (SDK-style), not paket pack, redirecting the Paket.Core strict reference to Fsharp.Core  #4260 hypothesis toward RestoreProcess.fs's plain <Version> emission (same root-cause class as Pinned version in nuspec for .NET Core projects #3557) rather than PackageMetaData.fs. No OS-conditional resolver code path found yet for Invalid resolution on macOS for 'monoandroid10.0' #3820. Neither issue reached a confident, surgical fix this run — no PR opened.

Generated by 🌈 Repo Assist, see workflow run.

Generated by 🌈 Repo Assist, see workflow run. Learn more.
_{Comment /repo-assist to run again}

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38

---

Run History — 2026-09 (run 33545918598)

• Task 1 (Issue Labelling): Applied labels to 30 previously unlabelled issues ("redirects: off" still sets AutoGenerateBindingRedirects to true #4158, Dependency manager looks up older tool version of paket #4164–Key not valid for use in specified state for windows containers #4170, Sporadic restore error with Microsoft.Web.WebView2 1.0.1343.22 #4176–paket update hangs on switching git branch #4212 range) based on title/body triage (mostly bug, some enhancement, question, documentation, needs triage).
• Task 3 (Issue Investigation and Fix): Investigated Could not detect any platforms warning #4239 ("Could not detect any platforms" for AWSSDK.Core's nonstandard .netcoreapp8.0 moniker). Confirmed root cause: netcoreapp6.0–10.0 monikers had no special-case handling (only netcoreapp5.0 was covered). Opened a draft PR adding the missing cases plus 6 new unit tests; all targeted tests passed (58/58 on net10.0; net461 pass unavailable due to missing mono in this sandbox). Linked a comment on the issue.
• Task 5 (Coding Improvements): Deferred this run in favor of completing the Task 3 fix; no separate improvement PR opened.

🤖 Automated update from Repo Assist.

Generated by 🌈 Repo Assist, see workflow run. Learn more.
_{Comment /repo-assist to run again}

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38

---

Run History — 2026-09 (run 33551731349)

• Task 1 (Issue Labelling): Labelled 11 previously unlabelled issues (Paket.Restore.targets error MSB4064: The "Readme" parameter is not supported by the "PackTask" task loaded from assembly: NuGet.Build.Tasks.Pack, Version=5.6.0.5, #4213, Paket outdated minor versions? #4214, paket.exe restore hangs after (successfully) finishing its job #4215, paket.exe never returns (even when just using paket.exe --version) #4216, Dependency wrongly parsed #4221, dotnet pack --symbols fails with error about Compile entry not containing Update or Include attribute #4222, Paket Restore Targets doesn't work with .NET 6+ #4223, Paket does not respect compatible versions of .Net Standard when adding references #4225, feat!(Paket.restore.targets): Support dotnet restore without paket restore; avoid null git diffs #4231, Paket integration with Visual Studio (and msbuild)  #4285, Behavior differs from VisualStudio if bulid/xxx.targets and bulid/native/xxx.targets are present #4304) with best-fit labels (bug, enhancement, question, needs triage, needs investigation).
• Task 2/3 (Investigation and Fix): Investigated dotnet pack --symbols fails with error about Compile entry not containing Update or Include attribute #4222 (dotnet pack --symbols crashes with "Compile entry is in unknown format" on <Compile Remove="..." /> items lacking Include/Update). Root cause confirmed: GetCompileItems didn't anticipate this valid MSBuild construct. Opened a draft PR fixing it (returns None via Seq.choose instead of throwing), with a new regression test in OutputSpecs.fs; build succeeded and 38/38 targeted tests passed. Posted a linking comment on the issue.

🤖 Automated update from Repo Assist.

Generated by 🌈 Repo Assist, see workflow run. Learn more.
_{Comment /repo-assist to run again}

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38

---

---

Run History — 2026-09 (run 33557543813)

• Task 3 (Issue Investigation and Fix): Investigated find-packages command fails when using UNC paths #4243 (find-packages fails on ~ home-directory local NuGet source paths). Root cause confirmed: Dependencies.FindPackagesByNameAsync (used by the find-packages CLI command) passed the raw local source path directly to Fake.Globbing.search without normalizing it, unlike NuGet.fs/NuGetLocal.fs which already call Utils.normalizeLocalPath. Opened a draft PR with the fix plus a new regression test in UtilsSpecs.fs; build succeeded and the new test passed (1/1). Posted a linking comment on the issue.
• Task 8 (Performance Improvements): Re-reviewed the codebase for low-risk performance wins; found none beyond the prior scan (no profiling data available). No action taken this run.
• Task 1 (Issue Labelling): Labelled 29 previously unlabelled issues (Exclude Paket incorporated analyzers from dotnet pack #4179–Behavior differs from VisualStudio if bulid/xxx.targets and bulid/native/xxx.targets are present #4304 range) with best-fit labels (bug, enhancement, question, documentation, needs investigation).

🤖 Automated update from Repo Assist.

Generated by 🌈 Repo Assist, see workflow run. Learn more.
_{Comment /repo-assist to run again}

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38