From 8b80b29a430184423e22a2207b33956b155b3147 Mon Sep 17 00:00:00 2001 From: Matthias Beyer Date: Sat, 9 Nov 2019 14:43:21 +0100 Subject: Add post: task-hookrs 0.7.0 --- content/blog/2019-11-09-task-hookrs-0-7-0.md | 29 ++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 content/blog/2019-11-09-task-hookrs-0-7-0.md diff --git a/content/blog/2019-11-09-task-hookrs-0-7-0.md b/content/blog/2019-11-09-task-hookrs-0-7-0.md new file mode 100644 index 0000000..ab47fd5 --- /dev/null +++ b/content/blog/2019-11-09-task-hookrs-0-7-0.md @@ -0,0 +1,29 @@ +--- +title: "task-hookrs v0.7.0" +date: "2019-11-09T14:45:40" +tags: ["library", "task-hookrs", "taskwarrior", "bindings"] +--- + +This is a short release announcement. `task-hookrs` was released in version `v0.7.0` +earlier this day. + +## Changelog for 0.7.0 + +* Bugfix: "imask" field in taskwarrior is a float, change type to f64. + This is a breaking API change, thus the minor version is bumped. +* CI setup was fixed to actually fail when an error happens during + compilation/testing. We had luck that it worked before without issue. +* All rustc versions from 1.32 until beta are tested now via travis, for maximum + backwards compat + + +## Further development + +Right now, no further development is planned for task-hookrs, as I consider this +library rather feature-complete. I'm not convinced that I should do a 1.0.0 +release, though. This is mainly due to the fact that I want to reserve the right +to break the API without the "uuh we are going from 1.0.0 to 2.0.0"-feeling. + +Pull requests and patches (via +[the mailinglist](https://imag-pim.org/maillinglist)) are welcome, of course! + -- cgit v1.2.3