Pulse v0.1.1 is the first release that moves beyond simply monitoring processes. The focus of this update is reliability and persistence, making Pulse more useful for services that are expected to run continuously.
The daemon has also been improved internally.
When Pulse is stopped, all managed processes are terminated cleanly and their PID information is removed automatically. This keeps the runtime environment predictable and avoids stale state from previous sessions.
Managing long-running services should feel straightforward, not fragile.
While most users will notice the new features, a large part of this release was spent improving the project's internals.
Several parts of the codebase were reorganized to make future development easier, reduce complexity, and prepare Pulse for larger features in upcoming releases.
Not every improvement is visible on the surface, but they make the project significantly easier to maintain.
Pulse is still in its early stages, but the direction is becoming clearer.
The goal has never been to build another heavyweight process manager. Pulse aims to stay lightweight, understandable, and easy to deploy while providing the tools needed to monitor services with confidence.
v0.1.1 is another step toward that goal.
As always, feedback, bug reports, and contributions are welcome. Every issue discovered today helps make the next release better.