| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
The fallback returns the macOS SDK version instead of the Xcode version, causing compatibility checks and diagnostics to use the wrong product version.
1 open issue 1 file not reviewedAdds an xcrun-based fallback to Xcode version detection, extending the platform compatibility checks introduced in #4221 for traced CodeQL analysis.
Changes:
| File | Description |
|---|---|
| src/platform.ts | Adds the command-based fallback and asynchronous detection wrapper. |
| src/platform.test.ts | Updates symlink tests and adds fallback coverage. |
| src/languages/traced.ts | Awaits Xcode detection before checking compatibility. |
Review effort: Balanced (auto)
Sorry, something went wrong.
…tsTracedAnalysis`
There was a problem hiding this comment.
No active review issues block approval of the macOS version-detection fallback changes.
No open issues 🎉
1 resolved since last review 1 file not reviewedReview effort: Balanced (auto)
Sorry, something went wrong.
There was a problem hiding this comment.
Two small things, otherwise LGTM
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Add-on to #4221 which adds a fallback for the Xcode version detection which calls out to xcrun.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
Products:
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist