Skip to content

docs(changelog): add #1716 and #1719 to 0.9.33 - #1720

Merged
rohitg00 merged 1 commit into
mainfrom
docs/0933-changelog-final
Nov 9, 2026
Merged

rohitg00 merged 1 commit into
mainfrom
docs/0933-changelog-final

Conversation

@rohitg00

@rohitg00 rohitg00 commented Nov 9, 2026

Copy link
Copy Markdown
Owner

Adds the two PRs merged after the 0.9.33 prep to its CHANGELOG section: the engine download retry (#1719) and the six-machine release gate (#1716). CHANGELOG only.

Signed-off-by: Rohit Ghumare <ghumare64@gmail.com>
@vercel

vercel Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
agentmemory Ready Ready Preview Nov 9, 2026 12:10pm UTC

Request Review

@coderabbitai

coderabbitai Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

Caution

Review failed

The pull request is closed.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Devin Review found 1 potential issue.

Devin Review

Comment thread CHANGELOG.md
- Consolidation keeps provenance and version heads across retries, and saved pattern memories reach the procedural tier (#1545, #1690). Reflection bounds its evidence and insight responses and keeps other projects' crystals out of a scoped reflection (#1544).
- `health` reports CPU relative to the machine's cores, not one core (#1286 by @DanielCarmingham).
- `agentmemory demo` stops the Compose workers it started on Windows (#1688 by @Mike-Animal-Counseling). Generated Compose values keep newlines (#1708 by @zhichao-poper).
- Fresh installs retry the iii engine download up to three times within two minutes on network errors, timeouts and HTTP 408, 429 and 5xx responses, and wait as long as `Retry-After` asks (#1719).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔍 Installer retry timing is overstated

A Retry-After: 180 response makes downloadToFile stop retrying, rather than wait 180 seconds. The initial download can also run for 300 seconds, so the two-minute limit applies to retry eligibility, not the entire download.

Devin Review


Was this helpful? React with 👍 or 👎 to provide feedback.

@rohitg00
rohitg00 merged commit 28ffc53 into main Nov 9, 2026
3 checks passed
@rohitg00
rohitg00 deleted the docs/0933-changelog-final branch November 9, 2026 12:10

This branch was successfully deployed

1 active deployment
Preview — b6d0c28e Deployed Nov 9, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant