Repository navigation
docs: record the conan/vcpkg blocker - #18
Merged
Merged
Conversation
Building a Conan fixture surfaced a hard blocker, filed upstream as trydrift/drift#185: `drift analyze` skips every Conan and vcpkg change with "target manifest range has no exact resolved registry version", before any analysis runs. parsePublishedVersion returns null for these two ecosystems and no others. That is deliberate — both let a package author its own version scheme, so a global ordering cannot be manufactured — but the same null also denies version *identity*, and triage() drops the change. The C/C++ header diff that capabilities.ts calls the strongest surface outside npm is therefore unreachable. The probe fixture was removed rather than committed, since it cannot work until that is separated upstream. Refs #6. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Building the Conan fixture surfaced a hard blocker. Filed upstream as
trydrift/drift#185.
drift analyzeskips every Conan and vcpkg change before any analysis runs:parsePublishedVersionreturnsnullfor these two ecosystems and no otherfourteen. That is deliberate — both let a package author its own version
scheme, and Drift declines to manufacture a global ordering. But the same
nullalso denies version identity, and
triage()then drops the change entirely.The effect is that
capabilities.tsadvertises a C/C++ header diff — which itcalls the strongest surface Drift has outside npm — plus full upgrade discovery,
and neither can ever run.
I built a real probe fixture (
fmt/9.1.0 → fmt/10.2.1) to confirm this, thenremoved it rather than commit a demo that cannot work.
docs/ecosystem-status.mdrecords the finding and the upstream link.
Refs #6.