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

0.79.1 release with updated gix dependency #13966

Closed
smoelius opened this issue May 26, 2024 · 2 comments
Closed

0.79.1 release with updated gix dependency #13966

smoelius opened this issue May 26, 2024 · 2 comments
Labels
A-git Area: anything dealing with git S-needs-info Status: Needs more info, such as a reproduction or more background for a feature request.

Comments

@smoelius
Copy link
Contributor

(Continued from #13950 (comment))

Would it be possible to get a 0.79.1 release with gix updated to version 0.63, as in these two PRs?

Currently, software that relies on cargo as a dependency triggers this warning: GHSA-7w47-3wg8-547c

Please forgive me as I don't know how labor intensive what I am asking for is.

@weihanglo
Copy link
Member

That requires some amount of cross-team collaboration. I don't have the permission to make a release. It also requires an extra stable backport, with an major update from gix@0.58.0 to gix@0.63.0. Due to some odd CI settings in this repo, a stable backport might require more efforts to figure out which set of changes need to be included (see #13925 as an example).

I am assuming that packages don't really use gitoxide feature when depending on cargo as a library. The actual risk should be quite low. And also cloning arbitrary repositories is always under risks and users need to scrutinize by themselves, as malicious build scripts could exist.

Does any package stop from compiling due to this, and have no way out? If not, I would recommend waiting for the 1.79.0 release on 2024-06-13.

@weihanglo weihanglo added A-git Area: anything dealing with git S-needs-info Status: Needs more info, such as a reproduction or more background for a feature request. labels May 28, 2024
@smoelius
Copy link
Contributor Author

@weihanglo Thanks very much for your reply. I had a hunch what I was asking for would be difficult.

Does any package stop from compiling due to this, and have no way out? If not, I would recommend waiting for the 1.79.0 release on 2024-06-13.

Not that I am aware of. I think your proposal makes sense. Thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-git Area: anything dealing with git S-needs-info Status: Needs more info, such as a reproduction or more background for a feature request.
Projects
None yet
Development

No branches or pull requests

2 participants