Skip to content

Commit 5ab0f16

Browse files
authored
Update CHANGELOG for version 0.6.5
Updated changelog for version 0.6.5, detailing fixes for cancellation Future marking in awaitCompletion and awaitAfterCancellation methods, and changes to error handling and Waker optimization.
1 parent fbc8f95 commit 5ab0f16

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

CHANGELOG.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
1111
- **`Scope::awaitCompletion()` not marking cancellation Future as used**: The cancellation token passed to `awaitCompletion()` was never marked with `RESULT_USED` / `EXC_CAUGHT`, causing a spurious "Future was never used" warning when the Future was destroyed. Additionally, early return paths (scope already finished, closed, or cancelled) skipped the marking entirely. Fixed by setting flags immediately after parameter parsing, before any early returns.
1212
- **`Scope::awaitAfterCancellation()` not marking cancellation Future as used**: Same issue as `awaitCompletion()` — the optional cancellation Future was only marked when the method reached `resume_when`, but early returns bypassed it. Fixed identically.
1313

14-
## [0.6.5] -
14+
## [0.6.5] - 2026-03-29
1515

1616
### Changed
1717
- **ZEND_ASYNC_SUSPEND** No longer throws an error when called with an empty array of events.
@@ -351,4 +351,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
351351
- Basic suspend/resume operations
352352
- Initial test framework
353353
- Context switching mechanisms
354-
- Basic scheduler implementation
354+
- Basic scheduler implementation

0 commit comments

Comments
 (0)