[repo-assist] Monthly Activity 2026-08

[github-actions]

Run 2026-09-01 — workflow run 33530423714

Selected tasks: 2 (Issue Investigation), 1 (Issue Labelling), 3 (Issue Fix)

• Task 1: Labelled 28 previously-unlabelled issues from the backlog (Unable to set up paket with visual studio for mac on macOS #3594–SetPaketCommand takes half a second #3836): mostly bug/question/enhancement, plus performance for SetPaketCommand takes half a second #3836, documentation for update does not behave as documened #3691, and needs triage for Paket with net core 3.0 fails #3678/Building fails due to missing fsc.exe #3679/Can't build simple roslyn code fix #3680.
• Task 2/3: Investigated several newly-labelled candidates:
  • dotnet tool paket clean cache issue #3781 (dotnet paket clean-cache breaks local dotnet-tool install): root-caused — Dependencies.ClearCache empties the global NuGet packages folder (UserNuGetPackagesFolder), which is the same folder the dotnet-tool infrastructure uses to locate the installed paket tool payload, so clearing it breaks subsequent dotnet paket invocations. Posted a root-cause comment with the known dotnet tool restore workaround; recommended a docs-only fix rather than changing clean-cache behavior, given the risk of masking real cache-clearing needs.
  • Paket show-installed-packages reports incorrect #3728 (show-installed-packages reports incorrect versions): could not reproduce from the description; a maintainer's 2019 request for a minimal repro was never answered. Recommended closing as stale/needs-more-info.
  • Could not detect any platforms from 'XCODE10' / 'XCODE11' #3816 / Could not detect any platforms warning #3703 (spurious "Could not detect any platforms" warnings for non-TFM build/ subfolders like XCODE10/Mono.Cecil/srcsrv): confirmed both share the same root cause in InstallModel.fs's build/ TFM scanner, which assumes every subfolder under build/ is a framework moniker. Posted a consolidated root-cause comment with a proposed fix direction (skip-not-warn for unparseable folder names with no matching build assets); flagged for maintainer sign-off before implementing, to avoid masking genuinely broken packages.
• No PR opened this run — none of the investigated issues had a low-risk, high-confidence surgical fix ready without further design input.
• Updated repo memory: cursor advanced to SetPaketCommand takes half a second #3836 (labelling) and corrected drift; removed Dotnet paket push doesn't work #3843 (merged via PR [repo-assist] Fix credential lookup for www.nuget.org / nuget.org mismatch (fixes #3843) #4418); recorded dotnet tool paket clean cache issue #3781/Paket show-installed-packages reports incorrect #3728/Could not detect any platforms from 'XCODE10' / 'XCODE11' #3816/Could not detect any platforms warning #3703 investigation outcomes; kept copy_local: true has no effect on netstandard projects #3810, Invalid resolution on macOS for 'monoandroid10.0' #3820, Xamarin and Java references wrongly added to load script? #3697, Behavior differs from VisualStudio if bulid/xxx.targets and bulid/native/xxx.targets are present #4304's native-targets follow-up as priorities.

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 2026-08-31 — workflow run 33349198298

Selected tasks: 3 (Issue Fix), 2 (Issue Investigation), 1 (Issue Labelling)

• Task 1: Labelled 11 previously-unlabelled issues (Paket pack doesn't escape square brackets #3906, Stack overflow with paket update on new project, apparently while resolving version conflicts from Nuget.Packaging 5.7 #3907, external_lock issues #3909, paket pack - unexpected 3rd party version constraint when not using --lock-dependencies  #3910, Paket install will replace existing Project on Circle CI #3912, dotnet tool install says paket 6.0.0-alpha042 is not compatible with net50 #3914, Latest alpha 042 doesn't seem to recognise net5.0 #3915, .Net 5 package resolution problems with some packages #3921, Exclude directories from processing #3923, Paket installs to global location rather that project root. #3924, Error during parsing of paket lock (linux builds) #3926) — mostly bug/question/enhancement, plus performance for Stack overflow with paket update on new project, apparently while resolving version conflicts from Nuget.Packaging 5.7 #3907 and needs triage for Paket install will replace existing Project on Circle CI #3912.
• Task 2/3: Investigated Paket pack doesn't escape square brackets #3906 ("paket pack doesn't escape square brackets"). Traced the packing pipeline (ensureValidName in NupkgWriter.fs) and confirmed that in the current codebase, packing a file named file[0].txt already produces a correctly escaped zip entry (file%5B0%5D.txt) — the reported bug does not reproduce as described. Rather than assume it's fully resolved, opened a draft PR adding a regression test locking in this behavior, and commented on the issue asking the reporter for their exact repro/version to confirm full closure.
• Also reviewed Unlisted Microsoft.Management.Infrastructure by default #3757 (resolver picks unlisted package version) and Does not produce a compatible lock file #3809 (warn on incompatible lock file) as Task 2 candidates but deferred further work — no live NuGet network access this run to verify Unlisted Microsoft.Management.Infrastructure by default #3757, and Does not produce a compatible lock file #3809 still needs deeper resolver review.
• Updated repo memory: advanced labelling cursor to Error during parsing of paket lock (linux builds) #3926, recorded Paket pack doesn't escape square brackets #3906 fix/investigation outcome, kept Unlisted Microsoft.Management.Infrastructure by default #3757/Does not produce a compatible lock file #3809 flagged as future priorities.

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

---

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 2026-08-31 — workflow run 33347057309

Selected tasks: 1 (Issue Labelling), 3 (Issue Fix), 2 (Issue Investigation)

• Task 1: Labelled 26 previously-unlabelled issues from the backlog (Unable to set up paket with visual studio for mac on macOS #3594–Versions in project.assets.json are different between restore and build #3825).
• Task 2: Investigated Directory specified is ignored...?: paket.references: "File: xyz.txt ." #3719 ("File: x . directory override seemingly ignored") — confirmed via the in-thread maintainer explanation this is by-design, not a bug: files linked via github dependencies always live under paket-files on disk, and the File: directory only controls where the linked reference appears in the project. Opened a small doc-clarity PR to disambiguate this in github-dependencies.md, and commented recommending closure. Also reviewed Update/Install re-adds content items if they have been modified to EmbeddedResource #1584 (2016 EmbeddedResource duplicate-content report) and recommended closing as stale/unreproducible on modern SDK-style projects.
• Task 3: Investigated Sub-command 'remove' fails on removal of last member of a group #2094 (paket remove fails removing last package of a non-main group) in depth — traced the root cause to a mismatch where DependenciesFile.RemovePackage prunes the emptied group from paket.dependencies but nothing prunes the corresponding group from paket.lock, causing a later GetGroup lookup to throw. Did not pin down the exact throwing call site with full confidence, so deferred implementing a fix this run (flagged in memory as a priority for a future run) rather than risk a low-quality patch.
• Updated repo memory: advanced labelling cursor to Versions in project.assets.json are different between restore and build #3825, added Directory specified is ignored...?: paket.references: "File: xyz.txt ." #3719/Update/Install re-adds content items if they have been modified to EmbeddedResource #1584 investigation outcomes, recorded Sub-command 'remove' fails on removal of last member of a group #2094 as a deferred fix candidate with root-cause notes.

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

---

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 2026-08-31 — workflow run 33342777233

Selected tasks: 4 (Engineering Investments), 2 (Issue Investigation), 3 (Issue Fix)

• Task 2/3 combined: Investigated open issues from the memory cursor (copy_local: true has no effect on netstandard projects #3810) forward. Reviewed Do not require setting proxy password in environment variable #3839, Error building on Windows only #3861, .net standard 2 does not seem to be included #3893 (not confident/actionable). Root-caused and fixed Dotnet paket push doesn't work #3843 ("Dotnet paket push doesn't work"): the documented add-token 'https://www.nuget.org' example stores credentials under www.nuget.org, but paket push's default lookup URL is nuget.org (no www), so the exact-match credential lookup never found the stored token. Opened a draft PR normalizing the www. prefix in ConfigFile.getSourceNodes, added a regression test, and commented on the issue linking the fix.
• Task 4: No outbound network access was available this run (curl to nuget.org blocked, Dependabot alerts API filtered), so dependency-version-based engineering work could not proceed. Effort was redirected to Task 2/3 investigation instead.
• Updated repo memory: advanced investigation cursor to Dotnet paket push doesn't work #3843, added fix record, cleaned up a stale resolved priority (fix-3785 PR merged), noted reviewed-but-not-actionable issues for future runs.

No new duplicate/stale items identified beyond the existing #4396/#4395 Task 6 note already in memory.

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-08-30 (latest run) — Run

• 🏷️ Labelled 18 previously-unlabelled issues from the 2019/2020 backlog (Unable to set up paket with visual studio for mac on macOS #3594–Paket does not seem to work with Azure Artifacts Credential Provider #3813): mostly bug/question, plus enhancement for NuGet / Paket Interop on transitive dependencies #3686, Nuget restore for AzureDevOps failed to authenticate on CI machine #3779, Don't output so much information by default #3790, and help wanted for Paket does not seem to work with Azure Artifacts Credential Provider #3813.
• 💬 Resolved Paket dependencies not added to build #3802: root-caused to an unsupported target framework in the referenced package, already explained in-thread in 2020; recommended closing (noted a separate paket init moniker nuance as a possible follow-up).
• 💬 Investigated Behavior differs from VisualStudio if bulid/xxx.targets and bulid/native/xxx.targets are present #4304 (targets file behavior differs from Visual Studio when both build/xxx.targets and build/native/xxx.targets are present): root-caused to InstallModel.fs lacking a build/native/ special case (unlike lib/native/), so the native-specific file is silently dropped while the plain build/*.targets file is always imported unconditionally. Posted a detailed root-cause + design-approach comment; deferred implementation pending maintainer sign-off given the scope (affects all projects' targets import generation).
• Deferred Does not produce a compatible lock file #3809 (warn on framework-incompatible package silently dropped from lock file) for a future run — needs a resolver/lock-file code review before deciding Fix vs. Comment.

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

---

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-08-30 (latest run) — Run

• 🏷️ Labelled 22 previously-unlabelled issues from the backlog (Error parsing project reference in project file #4193–Behavior differs from VisualStudio if bulid/xxx.targets and bulid/native/xxx.targets are present #4304), mostly bug/question, plus enhancement for Missing option to create/fill attribute GeneratePathProperty for element PackageReference #4194 (GeneratePathProperty request).
• 💬 Investigated Paket.Restore.targets created by paket.exe differs from GitHub release #3614 (Paket.Restore.targets version mismatch vs. released binary): root-caused to extractElement/extractRestoreTargets in RestoreProcess.fs, which always overwrites the targets file from the embedded assembly resource unless PAKET_SKIP_RESTORE_TARGETS=true. Recommended closing as by-design unless a genuine same-version mismatch can be reproduced.
• Re-checked Paket.Core strict reference to Fsharp.Core  #4260 (FSharp.Core dependency generated as = instead of >=): confirmed via the linked Paket.Core strict reference to Fsharp.Core 5.0 #4034 comment thread that this reproduces on modern Paket.Core (7.0.1+); still could not locate the exact SDK/PackageReference-driven code path that emits the exact-pin restriction (Paket.Core itself has no paket.template dependencies block), so no fix attempted this run. Remains an open Task 3 candidate.

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

---

2026-08-30 14:51 UTC — Run

• 🏷️ Labelled 10 previously-unlabelled issues from the 2020 no:label backlog: dotnet 3.1 always restores latest fsharp.core version #3769 (bug, needs investigation), Nuget restore for AzureDevOps failed to authenticate on CI machine #3779 (enhancement, credentials), dotnet tool paket clean cache issue #3781 (bug), paket pack framework groups #3782 (question), framework commentary #3785 (bug), and others in that range.
• 🐛 Root-caused and fixed paket.template dependency ~> LOCKEDVERSION gives inconsistent behaviour for x.y.0 versions #3727 (~> LOCKEDVERSION produces inconsistent version ranges depending on how many segments the locked version has, e.g. 0.68 vs 0.68.1): opened a draft PR normalizing the bare LOCKEDVERSION/CURRENTVERSION placeholder substitution to at least Major.Minor.Patch before it reaches the ~> twiddle parser, with 3 new regression tests (104/104 TemplateFile tests, 294/294 broader Version/Template tests passing on net9.0).
• 💬 Commented on paket.template dependency ~> LOCKEDVERSION gives inconsistent behaviour for x.y.0 versions #3727 with the root-cause analysis and a link to the fix PR.
• Re-investigated Paket.Core strict reference to Fsharp.Core  #4260 (Paket.Core's FSharp.Core dependency generated as = instead of >=): traced through PackageMetaData.fs's addDependency lock-file-driven version-requirement logic but could not yet confirm the exact code path responsible (Paket.Core has no explicit paket.template dependencies block, so the nuspec's FSharp.Core entry must come from an SDK/PackageReference-driven path not yet located). No fix attempted this run; remains an open investigation candidate.

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

---

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

Activity for August 2026

Suggested Actions for Maintainer

• Review PR: docs FAQ entry on magic-mode version caching — Repo Assist opened a draft PR this run.
• Review PR: ci: derive SDK version for dotnet-install.sh from global.json — Repo Assist opened a draft PR.
• Check comment paket 5.136.0 is not used in "magic" mode #3041: Repo Assist confirmed the "magic mode" version-caching explanation is still accurate and opened a FAQ doc PR; issue could be closed once the PR is merged — View
• Check comment Upgrading V9 to V10 causes dependency missing errors #4324: Repo Assist analysed PR Implement group conditions for SDK-style projects #4247's group-conditions restore changes and asked the reporter for the pre/post Paket versions and generated paket.props content — View
• Review PR: fix for Misleading error message: do not say "conflict" when package not found #3446 (misleading "conflict" wording when a package is simply not found) — Repo Assist opened a draft PR.
• Review PR: security fix pinning System.Formats.Asn1 to a patched version (NU1903 / CVE-2024-38095) — Repo Assist opened a draft PR.
• Review PR: coding cleanup removing a self-inflicted obsolete-API warning in PublicAPI.GetLibraries — Repo Assist opened a draft PR.
• 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] ci: add Linux scriptgen integration test job #4396: ci: add Linux scriptgen integration test job — Review
• Review PR [repo-assist] CI: enable scriptgen integration test suite as a required Linux job #4395: CI: enable scriptgen integration test suite as a required Linux job — Review
• Check comment dotnet clean ends up running paket restore #4262: Repo Assist explained why dotnet clean triggers PaketRestore (via CollectPackageReferences evaluation chain) and gave a PaketRestoreDisabled workaround — View
• Check comment paket restore does not properly populate the NuGet cache #3388: Repo Assist recommended closing as stale/obsolete (no repro since 2018, underlying SDK implicit-package mechanism has since changed) — View
• Check comment Paket 'hangs' without any output for several minutes #3412: Repo Assist investigated but could not root-cause the long-standing "paket hangs with no output" reports; asked for a process dump/stack trace to make progress — View
• Discuss: Pinned version in nuspec for .NET Core projects #3557 (pinned version lost in nuspec for SDK-style dotnet pack projects) — Repo Assist root-caused this to the .NET SDK's PackTask needing bracket syntax [x] to preserve an exact pin; proposed an opt-in fix, needs maintainer design sign-off before implementation.
• Decide: paket init should pin itself #3320 (paket init should pin its own version in generated paket.dependencies) — 2018 maintainer discussion leaned toward making pinning the default; still open, needs a maintainer decision before implementation.
• Check comment Paket.Restore.targets created by paket.exe differs from GitHub release #3614: Repo Assist root-caused the Paket.Restore.targets version-mismatch report to the always-overwrite-on-restore design in RestoreProcess.fs (with the PAKET_SKIP_RESTORE_TARGETS escape hatch) and recommended closing unless a genuine same-version mismatch can be reproduced — View

Future Work

• 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 before a fix can be attempted.
• 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 Error parsing project reference in project file #4193).

Run History

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