Releases: asterbloom/hotwatch
Releases · asterbloom/hotwatch
v0.5.0
- Breaking: Upgraded from
notifyv4 to v6, which substantially restructures theEventtype. Seenotify's CHANGELOG for more subtle behavior changes.
v0.4.6
- Removed unnecessary allocation from
util::handler_for_event.
v0.4.5
- The blocking implementation of
watchnow also acceptsFnMutinstead ofFn.
v0.4.4
watchnow acceptsFnMutinstead ofFn
v0.4.3
- Added
blockingAPI.
v0.4.2
- Re-export
notify. - Implemented
DebugforHotwatch. - Added
Hotwatch::new_with_custom_delay. - Added
Hotwatch::unwatch. - The background thread will now stop once
Hotwatchis dropped. - Updated docs and added an example.
- Removed dependency on
derive_moreandparking_lot.
v0.4.1
- Corrected doc links.
v0.4.0
This release removes the claim of compatability with Rust 1.24, as a patch update to notify changes the minimum requirement to 1.26.
hotwatch 0.3 can still be used with Rust 1.24 if you pin the notify dependency to 4.0.6.
- Only the latest stable release of Rust is guaranteed to be compatible.
hotwatch::Errornow implementsstd::error::Error.
v0.3.1
This release makes hotwatch seem significantly more like a legitimate crate.
hotwatchno longer requires nightly Rust! Minimum supported version is 1.24.- Uses
loginstead of obnoxiously usingprintln!. - Updated dependencies.
- Relicensed as dual Apache-2.0/MIT.
v0.3.0
This release includes a non-breaking API change and a potentially breaking behavior change.
Hotwatch::watchnow accepts any path type that satisfiesAsRef<Path>.- Paths are automatically canonicalized. This is to prevent surprising behavior with handler matching. As a result of this, the paths enclosed in
hotwatch::Eventvariants are now absolute, which can potentially break existing applications.