chore: 0.0.1a5 release #15
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,11 +1,33 @@ | ||
| # Changelog | ||
|
|
||
| ## 0.0.1a5 (2026-04-07) | ||
|
|
||
| Port fidelity release — 10 critical/high bugs fixed from systematic TS comparison. | ||
|
|
||
| ### Critical fixes | ||
| - Slack: multi-workspace token now persists into async tasks (ContextVar fix) | ||
| - Discord: slash command deferred responses now resolve correctly | ||
| - Discord: file attachments no longer silently dropped | ||
| - WhatsApp: media downloads work again (auth header restored) | ||
| - Chat: `on_lock_conflict="force"` now works | ||
|
|
||
| ### High fixes | ||
| - Discord: emoji normalized through resolver (reaction matching works) | ||
| - Teams: webhook options passed to reaction events | ||
| - Google Chat: subscription errors propagate to concurrent waiters | ||
| - Linear: fetch_thread metadata includes both key casings | ||
| - Streaming markdown `_remend` rewritten with proper delimiter tracking | ||
|
|
||
| ### Other improvements | ||
| - CLAUDE.md agent guidance file | ||
| - Parser: spaced thematic breaks (`* * *`) and trailing `#` stripping | ||
|
There was a problem hiding this comment. The trailing |
||
| - BaseFormatConverter: card fallback text generation | ||
| - All PR review comments addressed | ||
|
|
||
| ## 0.0.1a4 (2026-04-06) | ||
|
|
||
| Security hardening + launch documentation. | ||
|
|
||
| ## 0.0.1a3 (2026-04-06) | ||
|
|
||
| Initial alpha release — 8 adapters, 3 state backends, 2,467 tests. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
_remendimplementation instreaming_markdown.py(referenced here) has several issues that affect its fidelity:`). Markers like*or_inside inline code are incorrectly counted for balancing, which leads to broken markdown when a stream contains literal markdown characters inside code spans.\n\``to close unclosed code fences, even if the fence was opened with~~~`.[]for links but ignores the parentheses()for the URL part. A partially streamed link like[text](urlwill not be correctly closed.The implementation should be updated to strip inline code content before counting markers and to track the specific fence character used.