Skip to content

chore: release v0.1.3 #77

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
saucam merged 1 commit into from
Jul 2, 2026
Merged

chore: release v0.1.3 #77

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,35 @@ to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

## [0.1.3] - 2026-07-03

@coderabbitai coderabbitai Bot Jul 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Use the actual release date.

2026-07-03 is in the future relative to 2026-07-02, so this heading will be stale unless the tag is intentionally deferred.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` at line 9, The changelog heading for the 0.1.3 release uses a
future date, so update the release date in the top-level version entry to the
actual tag date before merging. Adjust the date in the release header for the
affected entry in CHANGELOG.md so it matches the real release timestamp and
stays current.


### Fixed

- **Daemon**: streamed assistant/thinking messages were pushed into scrollback
twice (stream start + finalize) — duplicating rows on every replay/attach,
splitting memory episodes into promptless halves, and drifting the byte
accounting negative so the 20MB scrollback cap never fired. Scrollback now
upserts by messageId with real UTF-8 byte accounting, and the transcript
`seq` counter resumes past the persisted tail instead of restarting at 0. (#74)
- **Web**: transcript virtualizer was never notified on count/session changes
(stale layout ghosting after session switches and size-cache poisoning — the
residual cause of the row-overlap bug #73 targeted); scrolled-past rows
leaked their DOM subtrees forever; `session.list` was ingested twice per
refresh and rebuilt every sidebar row; pending-approval and notification
watchers re-scanned the full transcript on every streaming delta; usage
analytics showed *global* totals to identities owning zero sessions and
broke past ~1000 sessions (SQLite variable limit); analytics chart mixed
local-time and UTC day buckets. (#75)
- **Telegram**: every streamed assistant/thinking block was delivered twice;
one unhandled handler error (e.g. `/ls` rendering an unescaped
`tool_running` status) permanently stopped long polling; flood-limited
(429) messages vanished silently — grammY auto-retry now honors
`retry_after`; interleaved broadcasts mid-stream dropped or duplicated
streamed text; >4000-char replies could arrive with chunks out of order;
tool completion/cancellation states never rendered; buffered content was
silently discarded on session switch/detach and stale broadcasts from a
detached session could write into the new session's chat. (#76)

Comment on lines +9 to +37

@coderabbitai coderabbitai Bot Jul 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Update the changelog compare links with the new release.

This new 0.1.3 section should be paired with a footer update ([Unreleased] → v0.1.3...HEAD, plus a [0.1.3] link) so the release history stays accurate.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 9 - 37, The new 0.1.3 changelog entry needs
matching compare links in the release footer so the history stays accurate.
Update the changelog footer to point the Unreleased link at v0.1.3...HEAD and
add the new [0.1.3] compare link; use the existing changelog link section around
the 0.1.3 heading as the place to keep these references consistent.

## [0.1.2] - 2026-06-28

### Fixed
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "codeoid",
"version": "0.1.2",
"version": "0.1.3",
"description": "Identity-first control plane for AI coding agents — multi-session, multi-frontend, with cross-session memory",
"type": "module",
"bin": {
Expand Down
Loading