chore: update package.json for v2.0.0-rc.3 release

[kriswest]

No description provided.

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	e0a889d
🔍 Latest deploy log	https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/68db5e5b12a9d20008734061

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.20%. Comparing base (7030df1) to head (e0a889d).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1233   +/-   ##
=======================================
  Coverage   84.20%   84.20%           
=======================================
  Files          68       68           
  Lines        2938     2938           
  Branches      374      374           
=======================================
  Hits         2474     2474           
  Misses        404      404           
  Partials       60       60           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kriswest]

@jescalada & @06kellyjac I've just failed to create the v2.0.0-rc.3 release and am going back to do it right by updating the version number first. However, I've just noticed the CLI package is stuck on version 0.1.0... In most mono repos I work on we keep the packages synced to the parent, because they all get released together and need to be used with matching verisons of each other. I think FDC3 uses https://jamiemason.github.io/syncpack/ to handle that.

Should I go ahead and update it to match?

[kriswest]

Updated it to match, you can just approve if you're happy with that and I'll release

[kriswest]

Well shucks:

41 passing (2m)
  1 failing

  1) test git-proxy-cli
       test git-proxy-cli :: version
         "--version" option prints version details :
     AssertionError: expected '2.0.0-rc.3\n' to include '0.1.0'
      at /home/runner/work/git-proxy/git-proxy/packages/git-proxy-cli/test/testCliUtils.js:45:27
      at Array.forEach (<anonymous>)
      at Object.<anonymous> (test/testCliUtils.js:44:24)
      at Generator.next (<anonymous>)
      at fulfilled (test/testCliUtils.js:5:58)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)

I'll have a poke at that tomorrow and either update the test or remove the version change