chore(deps): update dependency system.linq.async to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
System.Linq.Async	4.0.0 → 7.0.1

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • "on the 15th day of the month before 12pm"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report

[greptile-apps]

Greptile Summary

Renovate bot bumps System.Linq.Async from 4.0.0 to 7.0.0 in the test project (WorkOSTests.csproj). This is a major version jump across both the netcoreapp3.1 and net461 conditional ItemGroups.

• Compatibility concern: v7.0.0 introduces a transitive dependency on System.Linq.AsyncEnumerable (>= 10.0.0), which has known issues on older .NET Framework targets. The net461 build should be verified to compile cleanly.
• Unused dependency: No using System.Linq.Async directives were found in any .cs files in the repository, suggesting this package may not actually be needed and could be removed entirely instead of upgraded.
• Package status: System.Linq.Async is now marked as legacy by its maintainers in favor of the built-in System.Linq.AsyncEnumerable in .NET 10+.

Confidence Score: 3/5

• This PR carries moderate risk due to potential framework compatibility issues with net461 and a major version jump with new transitive dependencies.
• Score of 3 reflects that while the change is limited to test dependencies (reducing production risk), the major version bump from 4.x to 7.x introduces new transitive dependencies (System.Linq.AsyncEnumerable 10.0.0) that have documented compatibility issues on older .NET Framework targets. The net461 build may break, and the package may not even be needed.
• Pay close attention to test/WorkOSTests/WorkOSTests.csproj — verify the net461 build succeeds after this upgrade.

Important Files Changed

Filename	Overview
test/WorkOSTests/WorkOSTests.csproj	Updates System.Linq.Async from 4.0.0 to 7.0.0 for both netcoreapp3.1 and net461 targets. The new version introduces a transitive dependency on System.Linq.AsyncEnumerable which may cause build issues on net461, and the package itself is now considered legacy.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["WorkOSTests.csproj"] -->|"references"| B["System.Linq.Async 7.0.0"]
    B -->|"transitive dep"| C["System.Linq.AsyncEnumerable >= 10.0.0"]
    B -->|"transitive dep"| D["System.Interactive.Async >= 7.0.0"]
    A -->|"targets"| E["netcoreapp3.1"]
    A -->|"targets"| F["net461"]
    E -->|"resolves via"| G[".NET Standard 2.0"]
    F -->|"resolves via"| H[".NET Standard 2.0 / .NET Framework 4.8"]
    C -->|"may pull in"| I["Microsoft.Bcl.Memory"]
    I -->|"known issues on"| F
    style F fill:#ff9,stroke:#333
    style I fill:#f99,stroke:#333

Loading

_{Last reviewed commit: d32d54c}

[greptile-apps]

Potential compatibility risk with net461

System.Linq.Async v7.0.0 introduces a transitive dependency on System.Linq.AsyncEnumerable (>= 10.0.0), which has been reported to cause CS0518/CS0656 compile errors on older .NET Framework targets (specifically around System.Index). Since this project targets net461 (line 31), it would be worth verifying that the net461 build compiles successfully after this upgrade. The .NET Framework 4.8 target in the package should resolve to .NET Standard 2.0 for net461, but the transitive System.Linq.AsyncEnumerable dependency may pull in Microsoft.Bcl.Memory which can conflict on older frameworks.

Additionally, System.Linq.Async is no longer actively maintained and is considered legacy — the README now states: "You should no longer use this package." If this dependency isn't actively used (I couldn't find any using System.Linq.Async directives in the codebase), consider removing it entirely rather than upgrading.