NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io, #4961 most downloaded on crates.io
Library to execute commands in response to file modifications
Latest stable
8.4.4
Last release 1 months ago
06 Oct 2026
Release timing varies
gaps range from 2 weeks to 9 months
Most releases are documented
notes for 50 of the last 60 stable releases
7 versions withdrawn
withdrawn after publishing
10 years old
84 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
Fix crash on some error conditions.
4918b12)This also has creates two minor breaking changes:
The API now enables:
ArgsThis also has creates two minor breaking changes:
Args's paths field is now a Vec<PathBuf> rather than a Vec<String>cli::get_args() returns a Result rather than nothingThis was done in #105, prompted by #104 and #103.
This formalises the fix to #76.
Through setsid, thanks to @Mange (#102).
Fixes #47 and some other issues downstream.
These are hard to guess at / repro. Maybe it helped #99.
As part of the API changes, file-triggered runs and manual runs are now explicitly differentiated, which will help when eventually implementing #67.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
My bad. My changes related to whitespace handling completely broke several use cases, e.g.:
My bad. My changes related to whitespace handling completely broke several use cases, e.g.:
watchexec -- 'echo foo; echo bar'See discussion on #82.
This release reverts (comments out) those parts, but keeps everything else.
2: These changes also cause a breaking changes to the library interface, but this is not considered in the version numbers (i.e. if you use it, _pin i…
<sub> 1: Other changes were added following this to convert more panics into normal errors: some glob parsing errors, and file watcher initialisation errors.</sub>
<sub> 2: These changes also cause a breaking changes to the library interface, but this is not considered in the version numbers (i.e. if you use it, pin it). From cursory investigation only cargo-watch is a consumer and changes there in consequence are coordinated.</sub>
First release by @passcod! This release is merging in a variety of long-waiting improvements, but is otherwise fairly conservative.
First release by @passcod! This release is merging in a variety of long-waiting improvements, but is otherwise fairly conservative.
WATCHEXEC_*_PATH environment variables are now accurately documented — docsNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Behavior change: removes the default ./.* ignore pattern, as it was often surprising and usually not needed with .gitignore handling.
./.* ignore pattern, as it was often surprising and usually not needed with .gitignore handling.--no-default-ignore to explicitly disable all default ignores (@akerl)cargo watch.POSIX: Add --signal option to specify signal to send to child process (@chr4)
--signal option to specify signal to send to child process (@chr4)--no-shell option to exec() child process directly, instead of going through sh/cmd.exe (@chr4)Add -w/--watch option back to manually specify directories to watch. This is useful for cutting down on file descriptors used when watching deeply nes
-w/--watch option back to manually specify directories to watch. This is useful for cutting down on file descriptors used when watching deeply nested directory structures on Linux..gitignore files from all watched directories, and then search upwards in the directory hierarchy for any additional ones that need to be loaded. When watching multiple directories with a common parent, .gitignore files will only be loaded once..gitignore files found for each notification from the outside in.Unix: reap children upon receipt of SIGCHLD
-k option for sending SIGKILL to child processesUnix: Add -k option to send SIGKILL to child processes
-k option to send SIGKILL to child processesSIGTSTP/SIGCONT signals (used when you hit control-z in your shell for job control)Drop --watch option, as it has confusing semantics around where to find .gitignore files. If you need it, file an issue.
--watch option, as it has confusing semantics around where to find .gitignore files. If you need it, file an issue.Fix infinite loop when no .gitignore file found
.gitignore file foundnotify 3Automatically deployed release
Automatically deployed release
When waiting for all file system changes, de-dupe paths. This significantly reduces CPU for Linux users, as inotify sends a lot of notifications
Windows: launch child processes in a new job object, letting us kill all subprocesses
Search for .gitignore files in parent dirs
--run-initially flag.gitignore files in parent dirs$WATCHEXEC_UPDATED_PATH to the first updated path--force-poll optionNothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.