Skip to content
New issue

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

Update binsync dependency #1357

Merged
merged 2 commits into from
Nov 26, 2024
Merged

Update binsync dependency #1357

merged 2 commits into from
Nov 26, 2024

Conversation

spencerpogo
Copy link
Contributor

Closes #1356

@twizmwazin
Copy link
Member

I think I would prefer to keep with a pinned version rather than a >= requirement. A >= requirement is bound to cause an issue someday.

@spencerpogo
Copy link
Contributor Author

Agreed. Although this loses the information that we support 4.x, it is overall better

@twizmwazin
Copy link
Member

If compatibility with older versions is a concern, we can do a range. That being said I presume that users really only care about the latest.

@spencerpogo
Copy link
Contributor Author

No need for range I think it's fine as it stands right now

@twizmwazin twizmwazin merged commit aeabc49 into angr:master Nov 26, 2024
26 checks passed
@spencerpogo spencerpogo deleted the patch-1 branch November 27, 2024 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Depending on super old version of binsync for seemingly no reason
2 participants