Repository navigation
fix(deps): update fast-uri to 3.1.7 - #7245
Conversation
|
Depandabot Bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe fast-uri override changes from version 3.1.6 to 3.1.7 in the runner package and web workspace configuration. Changesfast-uri Override Update
Priority: ⬆️ High Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to The dependency update selects a version outside the identified advisory’s affected range. No actionable merge-blocking issue was established. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The update is consistently pinned in both applications, and no introduced security issue has been demonstrated. Risk cannot be assessed as minimal because the dependency’s reachable uses and their security controls have not been fully traced. Retained concerns Security review detailsSecurity Blast Radius
Security Findings and Attack Paths
Trust Boundaries and Controls
Hardening Proposals
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Website previewPreview URL: https://pr-7245-agenta-website-preview.mahmoud-637.workers.dev Built from |
Railway Preview Environment
Dependent tests finished. Post /preview for manual review. Environment absence verified; retained storage requires separate provider accounting. Post |
40ef031 to
7e16fcf
Compare
* feat(channels): inbound files on Slack, Telegram, and WhatsApp voice/video Pass inbound files to the agent as session attachments on every channel, reusing the WhatsApp media path: - WhatsApp: audio (voice notes) and video join image and document as media parts; only stickers, locations, and contact cards keep the fixed reply. - Telegram: photo, document, voice, audio, video, and video_note become media parts; fetch_media downloads through getFile with the bot token (deployment token on the hosted path); files.receive capability on at the Bot API's 20 MB cap. - Slack: each entry of a message's files array becomes a media part; fetch_media downloads url_private_download with the bot token and refuses an HTML login-page response. Attachment delivery downstream is unchanged: native images are inlined into the model prompt where supported, everything else lands as a file in the session working directory. OpenSpec change: channel-inbound-media. * refactor(channels): resolve Slack files at download time; one Telegram token hook Codex review follow-up on the inbound-media commit: - Slack stores only the file id on the inbox event; fetch_media resolves the current size and private URL through files.info at download time, so no private URL or size is persisted in channel_inbox_events. The mapping moves to slack/mapping.py next to the other pure mapping code, and a file-only share no longer carries an empty text part. - Telegram: one _api_token hook replaces _media_token; the base _call and fetch_media both read it, and the hosted adapter's _call override is deleted (it only swapped the token). - Telegram photo selection picks the largest size by area (file_size as tiebreaker) instead of trusting list order. - Tests: files.info resolution, no-URL refusal, file-only share shape, hosted deployment-token download, unordered photo sizes, and explicit project-scoping assertions on the dispatcher attachment path. - OpenSpec wording matches the code; README gains the change entry. * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(channels): keep the Telegram token out of download errors; name unnamed files A failed Telegram file download raised httpx's HTTPStatusError, whose message carries the request URL. That URL holds the bot token, and the inbox dispatcher logs the message, so a file that failed to download put a working token in the logs. Raise a status-only error instead. Files a platform sends without a name (Telegram photos, voice notes, video notes; WhatsApp images and voice notes) were stored as `image`, `audio`, or `video` with no extension. Name them `<kind>-<send time>.<ext>` from the message's send time and the detected type, so a retried dispatch keeps the same name. The spec now states that the platform attachment limit, not each channel's advertised max_bytes, is the effective cap. * fix(deps): update hono to 4.13.5 (#7249) * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(deps): update hono to 4.13.5 --------- Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update fast-uri to 3.1.7 (#7245) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs (#7252) * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs OpenAI released GPT-6.1 Sol (gpt-6.1-sol) at DevDay on 2026-09-29: $2/$10 per Mtok, $0.10 cached input, 272K context, near-Astra agentic coding at one fifth of Astra's price. Pi 0.99.1 (the direct successor of the pinned 0.87.1) carries it on the openai, azure, and openai-codex providers and makes it the Codex default. - Bump @earendil-works/pi-coding-agent and the pi-coding-agent-pi-ai alias to 0.99.1; update PINNED_PI_VERSION, the Daytona snapshot pin, and the provider-cost patch spec (new CLI chunk hash; both anchors verified to bind exactly once in 0.99.1). - Regenerate pi_models.generated.json from pi-ai 0.99.1 (541 -> 555 models; adds openai/gpt-6.1-sol, openai-codex/gpt-6.1-sol, the openrouter variants, and anthropic/claude-sonnet-5-5). - Retire the Sonnet 5.5 curated addition and its runner-side registration entry; pi 0.99.1 carries the model itself. - Add gpt-6.1-sol to supported_llm_models["openai"], PROVIDER_DEFAULT_MODELS["openai"], PI_SUBSCRIPTION_MODELS and the API's SUBSCRIPTION_PROVIDER_MODELS copy (first entry: it is Pi's new Codex default), plus curated overlay labels/descriptions/ratings. - Update the together_ai default Kimi-K2.7-Code -> Kimi-K3 (renamed in the pi-ai catalog). - Mirror Pi 0.99's bash-tool change in the in-process engine: a non-zero exit returns an isError result instead of throwing. Not in this change: the Codex harness. The pinned Codex CLI 0.156.1 is rejected by the ChatGPT backend for gpt-6.1-sol ("model is not supported when using Codex with a ChatGPT account", verified live); Codex 0.159.2 accepts it, but that needs a codex-acp 1.13.1 -> 2.x major bump, tracked separately. CODEX_MODELS is unchanged. Cost tracking needs no code change: the API prices spans from litellm's live price map, which already carries gpt-6.1-sol (verified: resolve_pricing_model("gpt-6.1-sol") prices 5031/10 tokens to $0.010062/$0.0001, matching Pi's billed numbers). * fix(sdk): replace retired Together AI Kimi K2.6 and K2.7-Code with Kimi K3 Pi 0.99.1 no longer lists the two Together AI Kimi models, and litellm's pinned registry never had them, so test_model_exists_in_litellm failed. Pi now lists together_ai/moonshotai/Kimi-K3 in their place. * chore(deps): bump undici from 8.10.0 to 8.10.2 in /services/runner (#7230) Bumps [undici](https://github.com/nodejs/undici) from 8.10.0 to 8.10.2. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v8.10.0...v8.10.2) --- updated-dependencies: - dependency-name: undici dependency-version: 8.10.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(deps): update image-size to 2.0.3 (#7246) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update mermaid to 11.16.1 --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Agenta Product Agent <team@agenta.ai> Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Agenta Product Agent <agent@agenta.ai> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* feat(channels): inbound files on Slack, Telegram, and WhatsApp voice/video Pass inbound files to the agent as session attachments on every channel, reusing the WhatsApp media path: - WhatsApp: audio (voice notes) and video join image and document as media parts; only stickers, locations, and contact cards keep the fixed reply. - Telegram: photo, document, voice, audio, video, and video_note become media parts; fetch_media downloads through getFile with the bot token (deployment token on the hosted path); files.receive capability on at the Bot API's 20 MB cap. - Slack: each entry of a message's files array becomes a media part; fetch_media downloads url_private_download with the bot token and refuses an HTML login-page response. Attachment delivery downstream is unchanged: native images are inlined into the model prompt where supported, everything else lands as a file in the session working directory. OpenSpec change: channel-inbound-media. * refactor(channels): resolve Slack files at download time; one Telegram token hook Codex review follow-up on the inbound-media commit: - Slack stores only the file id on the inbox event; fetch_media resolves the current size and private URL through files.info at download time, so no private URL or size is persisted in channel_inbox_events. The mapping moves to slack/mapping.py next to the other pure mapping code, and a file-only share no longer carries an empty text part. - Telegram: one _api_token hook replaces _media_token; the base _call and fetch_media both read it, and the hosted adapter's _call override is deleted (it only swapped the token). - Telegram photo selection picks the largest size by area (file_size as tiebreaker) instead of trusting list order. - Tests: files.info resolution, no-URL refusal, file-only share shape, hosted deployment-token download, unordered photo sizes, and explicit project-scoping assertions on the dispatcher attachment path. - OpenSpec wording matches the code; README gains the change entry. * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(channels): keep the Telegram token out of download errors; name unnamed files A failed Telegram file download raised httpx's HTTPStatusError, whose message carries the request URL. That URL holds the bot token, and the inbox dispatcher logs the message, so a file that failed to download put a working token in the logs. Raise a status-only error instead. Files a platform sends without a name (Telegram photos, voice notes, video notes; WhatsApp images and voice notes) were stored as `image`, `audio`, or `video` with no extension. Name them `<kind>-<send time>.<ext>` from the message's send time and the detected type, so a retried dispatch keeps the same name. The spec now states that the platform attachment limit, not each channel's advertised max_bytes, is the effective cap. * fix(deps): update hono to 4.13.5 (#7249) * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(deps): update hono to 4.13.5 --------- Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update fast-uri to 3.1.7 (#7245) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs (#7252) * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs OpenAI released GPT-6.1 Sol (gpt-6.1-sol) at DevDay on 2026-09-29: $2/$10 per Mtok, $0.10 cached input, 272K context, near-Astra agentic coding at one fifth of Astra's price. Pi 0.99.1 (the direct successor of the pinned 0.87.1) carries it on the openai, azure, and openai-codex providers and makes it the Codex default. - Bump @earendil-works/pi-coding-agent and the pi-coding-agent-pi-ai alias to 0.99.1; update PINNED_PI_VERSION, the Daytona snapshot pin, and the provider-cost patch spec (new CLI chunk hash; both anchors verified to bind exactly once in 0.99.1). - Regenerate pi_models.generated.json from pi-ai 0.99.1 (541 -> 555 models; adds openai/gpt-6.1-sol, openai-codex/gpt-6.1-sol, the openrouter variants, and anthropic/claude-sonnet-5-5). - Retire the Sonnet 5.5 curated addition and its runner-side registration entry; pi 0.99.1 carries the model itself. - Add gpt-6.1-sol to supported_llm_models["openai"], PROVIDER_DEFAULT_MODELS["openai"], PI_SUBSCRIPTION_MODELS and the API's SUBSCRIPTION_PROVIDER_MODELS copy (first entry: it is Pi's new Codex default), plus curated overlay labels/descriptions/ratings. - Update the together_ai default Kimi-K2.7-Code -> Kimi-K3 (renamed in the pi-ai catalog). - Mirror Pi 0.99's bash-tool change in the in-process engine: a non-zero exit returns an isError result instead of throwing. Not in this change: the Codex harness. The pinned Codex CLI 0.156.1 is rejected by the ChatGPT backend for gpt-6.1-sol ("model is not supported when using Codex with a ChatGPT account", verified live); Codex 0.159.2 accepts it, but that needs a codex-acp 1.13.1 -> 2.x major bump, tracked separately. CODEX_MODELS is unchanged. Cost tracking needs no code change: the API prices spans from litellm's live price map, which already carries gpt-6.1-sol (verified: resolve_pricing_model("gpt-6.1-sol") prices 5031/10 tokens to $0.010062/$0.0001, matching Pi's billed numbers). * fix(sdk): replace retired Together AI Kimi K2.6 and K2.7-Code with Kimi K3 Pi 0.99.1 no longer lists the two Together AI Kimi models, and litellm's pinned registry never had them, so test_model_exists_in_litellm failed. Pi now lists together_ai/moonshotai/Kimi-K3 in their place. * chore(deps): bump undici from 8.10.0 to 8.10.2 in /services/runner (#7230) Bumps [undici](https://github.com/nodejs/undici) from 8.10.0 to 8.10.2. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v8.10.0...v8.10.2) --- updated-dependencies: - dependency-name: undici dependency-version: 8.10.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(deps): update image-size to 2.0.3 (#7246) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update mermaid to 11.16.1 (#7253) * feat(channels): inbound files on Slack, Telegram, and WhatsApp voice/video Pass inbound files to the agent as session attachments on every channel, reusing the WhatsApp media path: - WhatsApp: audio (voice notes) and video join image and document as media parts; only stickers, locations, and contact cards keep the fixed reply. - Telegram: photo, document, voice, audio, video, and video_note become media parts; fetch_media downloads through getFile with the bot token (deployment token on the hosted path); files.receive capability on at the Bot API's 20 MB cap. - Slack: each entry of a message's files array becomes a media part; fetch_media downloads url_private_download with the bot token and refuses an HTML login-page response. Attachment delivery downstream is unchanged: native images are inlined into the model prompt where supported, everything else lands as a file in the session working directory. OpenSpec change: channel-inbound-media. * refactor(channels): resolve Slack files at download time; one Telegram token hook Codex review follow-up on the inbound-media commit: - Slack stores only the file id on the inbox event; fetch_media resolves the current size and private URL through files.info at download time, so no private URL or size is persisted in channel_inbox_events. The mapping moves to slack/mapping.py next to the other pure mapping code, and a file-only share no longer carries an empty text part. - Telegram: one _api_token hook replaces _media_token; the base _call and fetch_media both read it, and the hosted adapter's _call override is deleted (it only swapped the token). - Telegram photo selection picks the largest size by area (file_size as tiebreaker) instead of trusting list order. - Tests: files.info resolution, no-URL refusal, file-only share shape, hosted deployment-token download, unordered photo sizes, and explicit project-scoping assertions on the dispatcher attachment path. - OpenSpec wording matches the code; README gains the change entry. * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(channels): keep the Telegram token out of download errors; name unnamed files A failed Telegram file download raised httpx's HTTPStatusError, whose message carries the request URL. That URL holds the bot token, and the inbox dispatcher logs the message, so a file that failed to download put a working token in the logs. Raise a status-only error instead. Files a platform sends without a name (Telegram photos, voice notes, video notes; WhatsApp images and voice notes) were stored as `image`, `audio`, or `video` with no extension. Name them `<kind>-<send time>.<ext>` from the message's send time and the detected type, so a retried dispatch keeps the same name. The spec now states that the platform attachment limit, not each channel's advertised max_bytes, is the effective cap. * fix(deps): update hono to 4.13.5 (#7249) * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(deps): update hono to 4.13.5 --------- Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update fast-uri to 3.1.7 (#7245) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs (#7252) * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs OpenAI released GPT-6.1 Sol (gpt-6.1-sol) at DevDay on 2026-09-29: $2/$10 per Mtok, $0.10 cached input, 272K context, near-Astra agentic coding at one fifth of Astra's price. Pi 0.99.1 (the direct successor of the pinned 0.87.1) carries it on the openai, azure, and openai-codex providers and makes it the Codex default. - Bump @earendil-works/pi-coding-agent and the pi-coding-agent-pi-ai alias to 0.99.1; update PINNED_PI_VERSION, the Daytona snapshot pin, and the provider-cost patch spec (new CLI chunk hash; both anchors verified to bind exactly once in 0.99.1). - Regenerate pi_models.generated.json from pi-ai 0.99.1 (541 -> 555 models; adds openai/gpt-6.1-sol, openai-codex/gpt-6.1-sol, the openrouter variants, and anthropic/claude-sonnet-5-5). - Retire the Sonnet 5.5 curated addition and its runner-side registration entry; pi 0.99.1 carries the model itself. - Add gpt-6.1-sol to supported_llm_models["openai"], PROVIDER_DEFAULT_MODELS["openai"], PI_SUBSCRIPTION_MODELS and the API's SUBSCRIPTION_PROVIDER_MODELS copy (first entry: it is Pi's new Codex default), plus curated overlay labels/descriptions/ratings. - Update the together_ai default Kimi-K2.7-Code -> Kimi-K3 (renamed in the pi-ai catalog). - Mirror Pi 0.99's bash-tool change in the in-process engine: a non-zero exit returns an isError result instead of throwing. Not in this change: the Codex harness. The pinned Codex CLI 0.156.1 is rejected by the ChatGPT backend for gpt-6.1-sol ("model is not supported when using Codex with a ChatGPT account", verified live); Codex 0.159.2 accepts it, but that needs a codex-acp 1.13.1 -> 2.x major bump, tracked separately. CODEX_MODELS is unchanged. Cost tracking needs no code change: the API prices spans from litellm's live price map, which already carries gpt-6.1-sol (verified: resolve_pricing_model("gpt-6.1-sol") prices 5031/10 tokens to $0.010062/$0.0001, matching Pi's billed numbers). * fix(sdk): replace retired Together AI Kimi K2.6 and K2.7-Code with Kimi K3 Pi 0.99.1 no longer lists the two Together AI Kimi models, and litellm's pinned registry never had them, so test_model_exists_in_litellm failed. Pi now lists together_ai/moonshotai/Kimi-K3 in their place. * chore(deps): bump undici from 8.10.0 to 8.10.2 in /services/runner (#7230) Bumps [undici](https://github.com/nodejs/undici) from 8.10.0 to 8.10.2. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v8.10.0...v8.10.2) --- updated-dependencies: - dependency-name: undici dependency-version: 8.10.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(deps): update image-size to 2.0.3 (#7246) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update mermaid to 11.16.1 --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Agenta Product Agent <team@agenta.ai> Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Agenta Product Agent <agent@agenta.ai> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump axios from 1.18.0 to 1.20.0 in /web/tests (#7279) * chore(deps): bump axios from 1.18.0 to 1.20.0 in /web/tests Bumps [axios](https://github.com/axios/axios) from 1.18.0 to 1.20.0. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v1.18.0...v1.20.0) --- updated-dependencies: - dependency-name: axios dependency-version: 1.20.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> * chore(deps): update web lockfile for axios 1.20.0 --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Agenta Product Agent <team@agenta.ai> * fix(deps): update Pillow to 12.3.0 * fix(runner): install the sandbox lock with --no-deps so Pillow 12 can sit next to moviepy moviepy 2.2.1 (the latest) caps pillow<12, so the hash-locked install refused Pillow 12.3.0 and the runner image build failed. The lock is complete, so --no-deps installs it as written. Also lists every Pillow 12.3.0 wheel hash and drops the stale 11.3.0 ones. --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Agenta Product Agent <team@agenta.ai> Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Agenta Product Agent <agent@agenta.ai> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Summary
fast-urifrom 3.1.6 to 3.1.7 in the runner and web workspacesservices/runner/pnpm-lock.yamlandweb/pnpm-lock.yamlHetzner validation
Tested in isolated Docker worktrees based on
main(98ec6a27) with Node 24.Fix branch:
Unchanged
mainbaseline:The failures are verified pre-existing baseline failures; this change introduces no new test failures.