microsoft / microsoft/PSRule

Move to Sarif.Sdk greater then 2.4.16

Open
#1,470 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

.NET dependencies feature: core help wanted
Dominant language
C#
Stars
474
Forks
65
Avg merge
22h 25m
Merged PRs (30d)
26

Description

After Sarif.Sdk v2.4.16, the package reverted dependencies to only require a older version v9.0.1 (or newer) of Newtonsoft.Json then previously supported. This by default conflicts with Windows PowerShell because of the older style version pinning and binding redirects in .NET Framework.

Unfortunately we haven't been able to get this to work so far #1445.

While we still support Windows PowerShell we need to work around this. We're not going to drop support for Windows PowerShell with PSRule v3 but this will probably happen in v4.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing issue #1445 and the dependency and binding-redirect handling related to Sarif.Sdk and Newtonsoft.Json. Done means PSRule can move beyond Sarif.Sdk v2.4.16 while remaining compatible with Windows PowerShell.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, powershell
Domain
devtools, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.