We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As I understand it, when we are trying to understand the pinnings of packages, we are asked to look at external websites such as:
However, it seems like we should be able to build tools to extract this information ourselves between packages.
The question of did the ABI change between version "X" and "Y" should be answered by inspecting the package itself right?
did the ABI change between version "X" and "Y"
The text was updated successfully, but these errors were encountered:
This would remove one huge steps from merging migrations because our own bots could help us validate the assumptions we have.
Sorry, something went wrong.
ABI Compliance Checker list a few "similar tools" on its website, perhaps they are useful pointers: https://lvc.github.io/abi-compliance-checker/#Similar .
I like the idea!
No branches or pull requests
As I understand it, when we are trying to understand the pinnings of packages, we are asked to look at external websites such as:
However, it seems like we should be able to build tools to extract this information ourselves between packages.
The question of
did the ABI change between version "X" and "Y"
should be answered by inspecting the package itself right?The text was updated successfully, but these errors were encountered: