Release embassy-executor v0.7.0, embassy-time v0.4.0, embassy-time-driver v0.2.0.

1 files changed, 4 insertions, 5 deletions

diff --git a/embassy-executor/CHANGELOG.md b/embassy-executor/CHANGELOG.md
index ee8003a54..2c7f8c62e 100644
--- a/embassy-executor/CHANGELOG.md
+++ b/embassy-executor/CHANGELOG.md
@@ -5,13 +5,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## 0.7.0 - 2024-12-22
+## 0.7.0 - 2024-01-02
 
-- embassy-executor no longer provides an `embassy-time-queue-driver` implementation
+- Performance optimizations.
+- Remove feature `integrated-timers`. Starting with `embassy-time-driver` v0.2, `embassy-time` v0.4 the timer queue is now part of the time driver, so it's no longer the executor's responsibility. Therefore, `embassy-executor` no longer provides an `embassy-time-queue-driver` implementation.
+- Added the possibility for timer driver implementations to store arbitrary data in task headers. This can be used to make a timer queue intrusive list, similar to the previous `integrated-timers` feature. Payload size is controlled by the `timer-item-payload-size-X` features.
 - Added `TaskRef::executor` to obtain a reference to a task's executor
-- integrated-timers are no longer processed when polling the executor.
-- Added the option to store data in timer queue items
-- Added `timer-item-payload-size-X` features for time driver implementors
 
 ## 0.6.3 - 2024-11-12