-
Notifications
You must be signed in to change notification settings - Fork 215
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
notify failing on MacOS with new fsevent-sys
update
#314
Labels
Comments
This could be fixed by changing the
|
cc @erickt is this related to your recent PRs ? |
@0xpr03 - yeah, it looks like the API change I made to fsevent was done in a minor version, rather than major API change. I'll submit a fix. |
erickt
added a commit
to erickt/notify
that referenced
this issue
May 12, 2021
The latest released fsevents 3.2 made a breaking change in a minor version. Fixes notify-rs#314
0xpr03
pushed a commit
that referenced
this issue
May 12, 2021
The latest released fsevents 3.2 made a breaking change in a minor version. Fixes #314
Released as 5.0.0-pre.8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System details
rustc --version
: 1.52In
Cargo.toml
notify = { version = "5.0.0-pre.2", optional = true }
What you did (as detailed as you can)
On the bevy github page, our CI builds are failing due to a recent update within the
fsevent-sys
crate.See CI failures here;
What you expected
No CI failure on a simple minor release version change.
What happened
CI failed due to:
The text was updated successfully, but these errors were encountered: