fix: pin @stoplight/json dep to 3.20.0

[yjp20]

Addresses #2566

Checklist

• The basics
  • I tested these changes manually in my local or dev environment
• Tests
  • Added or updated
  • N/A
• Event Tracking
  • I added event tracking and followed the event tracking guidelines
  • N/A
• Error Reporting
  • I reported errors and followed the error reporting guidelines
  • N/A

[rattrayalex]

cc @chohmann – any chance you could give this a quick stamp? the bad dep causes things to be Very Broken.

[RobertCraigie]

cc @mnaumanali94 can anyone take a look at this? it's breaking everything for us

[mnaumanali94]

@RobertCraigie The team should be able to look at this tomorrow. We're in a bit of a transition in terms of ownership - we apologize for the wait.

[rattrayalex]

@mnaumanali94 anything we could do to persuade you to go ahead and release this? It's just a dependency pin to a previous-known-good version, and the breakage is quite bad (for us at least, and it seems, others too).

[mnaumanali94]

@rattrayalex This issue should be fixed now as a new version of stoplight/json should fix the error. Can y'all confirm please?

[rattrayalex]

Amazing, thank you @mnaumanali94 ! We'll give it a try shortly!

[RobertCraigie]

It looks like it's still failing but I haven't verified if this CI run is using the new stoplight/json version or not.

We've published a fork of prism-cli with the fix in this PR which is passing all our tests.

[mnaumanali94]

Is there a reason you are reverting to 3.20.0 and not 3.21.0?

[mnaumanali94]

Also trying on the command line with the steps to reproduce It doesn't fail. Can you see if the CI is using the right version?

[RobertCraigie]

@mnaumanali94 see this CI run which includes a debug log showing the versions of all deps.

It's using @stoplight/[email protected] and failing.

[Didel]

Resolves #2578

[lukaszzazulak]

@yjp20 sorry for the delay, could you resolve conflicts?