[release] v0.99.1#4271
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughSummary by CodeRabbit
WalkthroughMigrates Python projects from Poetry to uv (pyproject/uv.lock, build-system, CI, Dockerfiles, check_deps, docs, tests), bumps multiple package versions to 0.99.1, updates frontend JS dependency pins, and adds runtime tuning and FastAPI response/middleware. ChangesBuild-system migration: Poetry → uv (pyproject, uv.lock, CI, Docker, check_deps, docs, tests)
Web frontend manifest updates
Runtime startup tuning & FastAPI response/middleware
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the Comment |
…may-2026 [Chore] Update FE dependencies to resolve dependabot issues
[chore] Move to uvloop and httptools
[chore] Bump to python 3.13 / debian 13
There was a problem hiding this comment.
Actionable comments posted: 3
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 84c23ca1-4059-4ecf-8071-35e27d833b81
⛔ Files ignored due to path filters (1)
web/pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (9)
examples/python/RAG_QA_chatbot/frontend/package.jsonweb/ee/package.jsonweb/oss/package.jsonweb/package.jsonweb/packages/agenta-entities/package.jsonweb/packages/agenta-entity-ui/package.jsonweb/packages/agenta-shared/package.jsonweb/packages/agenta-ui/package.jsonweb/tests/package.json
✅ Files skipped from review due to trivial changes (1)
- examples/python/RAG_QA_chatbot/frontend/package.json
🚧 Files skipped from review as they are similar to previous changes (3)
- web/package.json
- web/oss/package.json
- web/ee/package.json
Railway Preview Environment
Updated at 2026-05-06T10:06:43.732Z |
[chore] Include typical FastAPI speedups
[chore] Migrate from poetry to uv
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (3)
hosting/docker-compose/oss/docker-compose.gh.yml (1)
41-43: ⚡ Quick winRemove
--worker-connectionsflag—it has no effect withuvicorn.workers.UvicornWorker.Gunicorn's
--worker-connectionssetting only affectsgthread,eventlet, andgeventworkers. When usinguvicorn.workers.UvicornWorker, concurrency is managed by Uvicorn's event loop, not Gunicorn's worker connections. The UvicornWorker does not map this setting to Uvicorn's configuration, making it a no-op that creates false assumptions about capacity tuning..github/workflows/01-create-release-branch.yml (1)
82-90: ⚡ Quick winAvoid syncing three environments just to compute the next version.
uv version --bumpupdates the project and, by default, also locks and syncs it. In this workflow, that meanssdk,api, andserviceseach pay for an unnecessary environment sync just to compute the next version. Adding--no-synckeeps the version update while removing extra network / venv work. (docs.astral.sh)Suggested change
- SDK_VERSION=$(uv version --bump "$BUMP_TYPE" --short) + SDK_VERSION=$(uv version --bump "$BUMP_TYPE" --short --no-sync) cd .. cd api - API_VERSION=$(uv version --bump "$BUMP_TYPE" --short) + API_VERSION=$(uv version --bump "$BUMP_TYPE" --short --no-sync) cd .. cd services - SERVICES_VERSION=$(uv version --bump "$BUMP_TYPE" --short) + SERVICES_VERSION=$(uv version --bump "$BUMP_TYPE" --short --no-sync) cd ...github/workflows/44-railway-tests.yml (1)
350-355: ⚡ Quick winAlign these
uv syncinstalls with the 3.13 release runtime.This PR moves the shipped Docker images to Python 3.13, but both Railway jobs still resolve and install their environments against 3.11. If these jobs are meant to gate the release runtime, they can miss 3.13-only dependency or behavior regressions.
Also applies to: 450-455
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 8ccd7751-649b-4838-ba1b-ea22aef0beff
⛔ Files ignored due to path filters (6)
api/poetry.lockis excluded by!**/*.lockapi/uv.lockis excluded by!**/*.locksdk/poetry.lockis excluded by!**/*.locksdk/uv.lockis excluded by!**/*.lockservices/poetry.lockis excluded by!**/*.lockservices/uv.lockis excluded by!**/*.lock
📒 Files selected for processing (32)
.github/workflows/01-create-release-branch.yml.github/workflows/11-check-code-styling.yml.github/workflows/12-check-unit-tests.yml.github/workflows/44-railway-tests.ymlapi/check_deps.pyapi/ee/docker/Dockerfile.devapi/ee/docker/Dockerfile.ghapi/entrypoints/routers.pyapi/oss/docker/Dockerfile.devapi/oss/docker/Dockerfile.ghapi/pyproject.tomldocs/designs/testing/README.mddocs/docs/contributing/guides/testing.mdxhosting/docker-compose/ee/docker-compose.dev.ymlhosting/docker-compose/ee/docker-compose.gh.local.ymlhosting/docker-compose/ee/docker-compose.gh.ymlhosting/docker-compose/oss/docker-compose.dev.ymlhosting/docker-compose/oss/docker-compose.gh.local.ymlhosting/docker-compose/oss/docker-compose.gh.ssl.ymlhosting/docker-compose/oss/docker-compose.gh.ymlhosting/railway/oss/api/Dockerfilesdk/__init__.pysdk/check_deps.pysdk/oss/tests/pytest/unit/README.mdsdk/oss/tests/pytest/unit/TESTING_PATTERNS.mdsdk/pyproject.tomlservices/check_deps.pyservices/ee/docker/Dockerfile.devservices/ee/docker/Dockerfile.ghservices/oss/docker/Dockerfile.devservices/oss/docker/Dockerfile.ghservices/pyproject.toml
✅ Files skipped from review due to trivial changes (3)
- .github/workflows/11-check-code-styling.yml
- api/pyproject.toml
- sdk/oss/tests/pytest/unit/README.md
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/docs/contributing/guides/testing.mdx (1)
55-63:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winUse
uv run pytestfor API commands to avoid interpreter mismatch.After
uv sync,python -m pytestcan hit the wrong interpreter unless a venv is manually activated. Usinguv runhere keeps execution consistent with the rest of the guide.Suggested doc patch
- python -m pytest oss/tests/pytest/ -v + uv run pytest oss/tests/pytest/ -v- python -m pytest oss/tests/pytest/acceptance/workflows/ -v + uv run pytest oss/tests/pytest/acceptance/workflows/ -v
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: c55bfc45-c8e2-4498-a22a-6e1525095ef1
📒 Files selected for processing (2)
docs/designs/testing/README.mddocs/docs/contributing/guides/testing.mdx
Replace exact-pinned "1.13.5" with ">=1.13.5 <2.0.0" in peerDependencies for agenta-entities, agenta-entity-ui, and agenta-shared to prevent peer resolution conflicts with workspace packages already on axios 1.16.0. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: b98b41c9-6369-42c7-9baf-5988dccba53c
📒 Files selected for processing (3)
web/packages/agenta-entities/package.jsonweb/packages/agenta-entity-ui/package.jsonweb/packages/agenta-shared/package.json
New version v0.99.1 in