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 jni #33

Merged
merged 1 commit into from
Aug 10, 2021
Merged

Update jni #33

merged 1 commit into from
Aug 10, 2021

Conversation

DJMcNab
Copy link
Contributor

@DJMcNab DJMcNab commented Aug 9, 2021

Bevy's cargo deny check failed because cpal depends on jni directly and via this crate.

This meant that there were multiple jni versions in our tree.

Please note that I haven't tested this, and haven't managed to build locally, so I'm going to see what CI says first - hopefully it will go through without issue.

This borked bevy's cargo deny check because cpal
depends on jni directly and via this crate so there
were multiple versions
@katyo katyo merged commit 101d4a9 into katyo:master Aug 10, 2021
@DJMcNab
Copy link
Contributor Author

DJMcNab commented Aug 17, 2021

@katyo would it be possible to get a release containing this please?

It's still causing the issue for bevy (to clarify, it's not blocking anything, it's just muddying CI status).

If you don't think this is a semver compatible change, then I don't want to push for a major release just for this dependency - I'm unclear how much jni influences the public interface.

Of potential note here is that cpal upgraded their jni version in a patch release, and don't seem to have had any problems there

@katyo
Copy link
Owner

katyo commented Aug 18, 2021

@DJMcNab version 0.4.3 issued on crates.io!

@katyo
Copy link
Owner

katyo commented Aug 18, 2021

@DJMcNab Unfortunately I forget to update pre-generated bindings... I will issue 0.4.4 for now.

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.

2 participants