chore(main): release 0.2.0 by github-actions[bot] · Pull Request #326 · scaleapi/scale-agentex

github-actions · 2026-06-19T02:22:10Z

🤖 I have created a release beep boop

0.2.0 (2026-09-15)

Features

agent_api_keys: one-call webhook-trigger setup endpoint (#329) (9cc71fb)
agentex-ui: accept RSA (RS256) private_key_jwt keys (#367) (e2c8a22)
agentex-ui: account picker via same-origin BFF proxy (#350) (0f07dc7)
agentex-ui: grow chat input vertically for multi-line prompts (#332) (8c060f1)
agentex-ui: OIDC login with server-side access token (#351) (824286c)
agentex: add Slack Events API url_verification endpoint (#369) (d0ba8bf)
agentex: DM unlinked Slack users a link to connect their account (#412) (6101ea4)
agentex: filter GET /agents by agent card metadata (#411) (b0e3443)
agentex: forward OIDC bearer credential for user delegation (#363) (cea5963)
agentex: golden-agent self-posts its Slack reply; gateway skips relay (#405) (a3c674e)
agentex: identity-link storage with encrypted credentials at rest (#409) (9f8d539)
agentex: Linear gateway — invoke agents from Linear (#399) (4718eee)
agentex: Linear gateway — invoke agents from Linear (re-land) (#401) (fc835c0)
agentex: run Slack turns as the invoking user, and the flow to link them (#410) (c0cad3c)
agentex: Slack /agents modal to pick an agent and dispatch (#404) (fb07098)
agentex: Slack gateway — invoke agents from Slack (#388) (8043a3b)
agentex: support SYNC agents in the Slack gateway (#392) (28a1a00)
dev: ignore local Neovim config files (#413) (a409ff2)
dev: run agentex locally without Docker (#353) (f2c3fd9)
observability: RPC + workflow + DB-pool metrics for the agent JSON-RPC endpoint (#379) (80763f7)
retention: strict bool env parsing + stale-RUNNING cleanup override (#306) (5ad81e8)
schedules: add exact skip and unskip actions (#357) (ac88134)
schedules: agent run schedules (v1) (#335) (6a66ad3)
states: add storage-phase config and task-state repository selector (#380) (354f35e)
task-messages: add optional is_error to ToolResponseContent (#331) (5020e96)
tasks: add task-stream lifecycle metrics (#387) (6b9e58f)
tasks: non-terminal task/interrupt + INTERRUPTED status (AGX1-391) (#365) (a92081a)
ui: add scheduled task management (#354) (0d859c2)
ui: improve scheduled task controls (#378) (b5a1d17)
update task configs in agentex db on turn (#309) (13eea7a)
webhooks: accept Authorization: AgentKey on forward routes (#402) (dbd5b2c)

Bug Fixes

acp: forward allowlisted client headers on all ACP paths (#384) (2c2d5c8)
acp: forward W3C trace-context headers to downstream agents (#396) (e5f13ba)
agentex-ui: abort the upstream request when the BFF client disconnects (#383) (c729b12)
agentex-ui: bump nanoid 3.3.16 -> 3.3.18 (CVE-2026-67213) (#398) (e472bcc)
agentex-ui: bump next 15.5.18 -> 15.5.21 (8 CVEs) (#375) (2c27100)
agentex-ui: bump next 15.5.21 to 15.5.24 and sharp 0.35.3 to 0.35.4 (#424) (14a9f21)
agentex-ui: bump next-auth 5.0.0-beta.31 -> 5.0.0-beta.32 (4 CVEs) (#376) (d355c92)
agentex-ui: bump postcss 8.5.19 -> 8.5.25 (CVE-2026-69153) (#395) (4d805e4)
agentex-ui: bump postcss to >=8.5.10 (CVE-2026-41305) (#360) (8e5159b)
agentex-ui: bump sharp 0.34.3 -> 0.35.3 (GHSA-f88m-g3jw-g9cj) (#371) (ffa5f94)
agentex-ui: bump tar 7.5.11 -> 7.5.16 (CVE-2026-53655) (#361) (f8e64a1)
agentex-ui: bump tar 7.5.20 -> 7.5.22 (GHSA-r292-9mhp-454m) (#382) (32a9acc)
agentex-ui: bump uuid 11.1.0 -> 11.1.1 (CVE-2026-41907) (#362) (9edebf5)
agentex-ui: merge URL updates against the live URL to fix account-switch races (#355) (f87e363)
agentex-ui: stop clipping agent badge hover scale and shadow (#352) (b49fab6)
agentex: /agents left a stray {} in the channel (#418) (a8a54c1)
agentex: bump aiohttp 3.13.4 -> 3.14.1 (clears 11 CVEs, agentex server image) (#359) (3001351)
agentex: bump aiohttp 3.14.1 -> 3.14.3 (clears 3 CVEs, agentex server image) (#393) (a167690)
agentex: bump ddtrace to >=4.8.2 (CVE-2026-50271) (#364) (2913fe0)
agentex: bump h2 4.3.0 -> 4.4.1 (CVE-2026-71554) (#397) (6de0def)
agentex: end SSE subscriptions on terminal task / vanished topic; stop deleting shared stream (#385) (0011d2c)
agentex: give each linked Slack user their own agent config (#420) (a1840b7)
agentex: recover unhealthy agents after successful probes (#417) (5b4d188)
agentex: rejected sessions prompt a re-link, unlinked turns stop pretending, and linking answers the pending question (#416) (43a1c06)
agentex: tell a user when SGP won't let their account hold a Slack config (#422) (53f82a2)
agentex: the link offer described one agent's tools, not what linking does (#419) (a96c48e)
authz: fall back to body principal in _register_in_auth (#373) (ad0231c)
authz: grant legacy agent register principal (#325) (cae5f94)
deps: cap fastapi <0.137.0 to stop OPTIONS preflight 500s (#334) (acbe9e3)
deps: clear golden-image Trivy CRITICAL/HIGH (litellm, starlette, pyjwt, python-multipart) (#320) (bfa6652)
observability: isolate SSE stream spans and continue ingress traceparent (#390) (b3a301d)
page ready agents during health-check startup (#345) (2ffde24)
schedules: backfill agent_run_schedules deleted_at/version on early-deployed envs (#341) (fc1ba55)
schedules: grant legacy auth for run schedules (#344) (648e81c)
schedules: include timezone data in backend image (#370) (2c4f061)
schedules: load live fields in schedule lists (#368) (c045ad0)
schedules: use stable handles for run schedules (#349) (3b722f6)
streams: cut SSE error-log volume and add Redis pool headroom (#340) (352eaaa)
streams: snapshot SSE cursor before "connected" to stop first-token drops (#330) (7c2ccfd)
tasks: omit params from the list-tasks response (#377) (e62a2a7)
tasks: preserve task_metadata in combined update and forward merge_params by name (#336) (8c25c64)
ui: load all agents so the picker and deep-links work past the first page (#347) (92b9da3)
ui: manually created tasks render as "Unnamed task" in the sidebar (#407) (304f014)
ui: scheduled-tasks UAT fixes — modals, display corrections, UX polish (#403) (e8e962f)
ui: thinking indicator never clears on a failed task (#408) (ef3a237)

Documentation

document Redis as a required dependency (#343) (4c1740b)
guides: tracing, framework-agent, and local-sandbox guides (#339) (b43e8c3)
streaming: document the unified harness surface (#337) (31fd697)

Refactors

agentex: shrink identity-link config, surface the connect link, stop leaking ids (#414) (e5a2a32)
agentex: Slack gateway reads bot credentials from env, not DB (#394) (3d1817c)

This PR was generated with Release Please. See documentation.

Confidence Score: 4/5

This PR is not ready to merge. The frozen lockfile is still stale, and the changelog exposes an internal ticket ID.

Findings

Regenerate the lockfile ▶
Regenerate frozen lockfile ▶

Fix with agent prompt

### Issue 1
pyproject.toml:undefined-3
The package versions were bumped here and in `agentex/pyproject.toml`, but `uv.lock` still records both workspace packages as `0.1.0` (`agentex` and `agentex-backend`). The Docker build copies that lockfile and runs `uv sync --frozen --no-dev --package agentex-backend` and `uv export --frozen`, so the release image path can fail the frozen-lock freshness check or install/export package metadata from the previous version. Regenerate and commit `uv.lock` with the `0.1.1` package versions.

### Issue 2
pyproject.toml:undefined-3
This release bumps the workspace package to `0.2.0`, but `uv.lock` still records both `agentex` and `agentex-backend` as `0.1.0`. The Docker image copies that lockfile and runs frozen `uv export` / `uv sync` for `agentex-backend`, so the release build can fail the frozen-lock check or install/export package metadata for the previous version instead of this release.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This release moves Agentex from version 0.1.0 to 0.2.0 across its packages, runtime version, release metadata, and API description. It also adds a changelog that groups the features, fixes, documentation, and refactors included in the release.

Updates release, package, runtime, and API version sources to 0.2.0.
Adds the 0.2.0 changelog and release date.
Regenerates the API description as part of the release.

Diagram

sequenceDiagram
    participant RP as Release Please
    participant M as Version files
    participant O as OpenAPI contract
    participant C as Changelog
    participant L as uv.lock
    RP->>M: Set package version to 0.2.0
    RP->>O: Regenerate contract at 0.2.0
    RP->>C: Add 0.2.0 release notes
    Note over L: Still records workspace packages at 0.1.0

_{Reviews (81) · Last reviewed commit: "chore(main): release 0.2.0"}

greptile-apps · 2026-06-22T17:08:56Z

 [project]
 name = "agentex"
-version = "0.1.0"
+version = "0.1.1"


Regenerate the lockfile

The package versions were bumped here and in agentex/pyproject.toml, but uv.lock still records both workspace packages as 0.1.0 (agentex and agentex-backend). The Docker build copies that lockfile and runs uv sync --frozen --no-dev --package agentex-backend and uv export --frozen, so the release image path can fail the frozen-lock freshness check or install/export package metadata from the previous version. Regenerate and commit uv.lock with the 0.1.1 package versions.

Artifacts

Repro: lock metadata check script

Contains supporting evidence from the run (text/x-python; charset=utf-8).

Repro: lock metadata check output showing stale package versions

Keeps the command output available without making the summary code-heavy.

Repro: attempted frozen uv sync command output

Keeps the command output available without making the summary code-heavy.

Repro: attempted frozen uv export command output

Keeps the command output available without making the summary code-heavy.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review. Path: pyproject.toml Line: 3 Comment: **Regenerate the lockfile** The package versions were bumped here and in `agentex/pyproject.toml`, but `uv.lock` still records both workspace packages as `0.1.0` (`agentex` and `agentex-backend`). The Docker build copies that lockfile and runs `uv sync --frozen --no-dev --package agentex-backend` and `uv export --frozen`, so the release image path can fail the frozen-lock freshness check or install/export package metadata from the previous version. Regenerate and commit `uv.lock` with the `0.1.1` package versions. How can I resolve this? If you propose a fix, please make it concise.

github-actions · 2026-06-24T17:58:01Z

✱ Stainless preview builds

This PR will update the agentex-sdk SDKs with the following commit messages.

openapi

chore(main): release 0.2.0

python

chore(main): release 0.2.0

typescript

chore(internal): regenerate SDK with no functional changes

Edit this comment to update them. They will appear in their respective SDK's changelogs.

✅ agentex-sdk-openapi studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅

✅ agentex-sdk-typescript studio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️ → build ⏭️ (prev: build ✅) → lint ⏭️ (prev: lint ✅) → test ✅

⚡ agentex-sdk-python studio · conflict

Your SDK build resulted in a merge conflict between your custom code and the newly generated changes, which is a regression from the base state.
You don't need to resolve this conflict right now, but you will need to resolve it for your changes to be released to your users. Read more about why this happened here.

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-06-25 18:06:43 UTC

greptile-apps · 2026-06-25T15:57:32Z

 [project]
 name = "agentex"
-version = "0.1.0"
+version = "0.2.0"


Regenerate frozen lockfile

This release bumps the workspace package to 0.2.0, but uv.lock still records both agentex and agentex-backend as 0.1.0. The Docker image copies that lockfile and runs frozen uv export / uv sync for agentex-backend, so the release build can fail the frozen-lock check or install/export package metadata for the previous version instead of this release.

Artifacts

Repro: generated frozen uv check script

Contains supporting evidence from the run (text/x-shellscript; charset=utf-8).

Repro: frozen uv command output showing stale lockfile validation failure

Keeps the command output available without making the summary code-heavy.

Repro: uv 0.7.3 installation output used to run the frozen checks

Keeps the command output available without making the summary code-heavy.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review. Path: pyproject.toml Line: 3 Comment: **Regenerate frozen lockfile** This release bumps the workspace package to `0.2.0`, but `uv.lock` still records both `agentex` and `agentex-backend` as `0.1.0`. The Docker image copies that lockfile and runs frozen `uv export` / `uv sync` for `agentex-backend`, so the release build can fail the frozen-lock check or install/export package metadata for the previous version instead of this release. How can I resolve this? If you propose a fix, please make it concise.

github-actions Bot requested a review from a team as a code owner June 19, 2026 02:22

github-actions Bot added the autorelease: pending label Jun 19, 2026

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch from 63c1abc to 34c3cdd Compare June 22, 2026 17:01

greptile-apps Bot reviewed Jun 22, 2026

View reviewed changes

github-actions Bot changed the title ~~chore(main): release 0.1.1~~ chore(main): release 0.2.0 Jun 22, 2026

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch 5 times, most recently from e158b69 to d1cae87 Compare June 23, 2026 21:06

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch from d1cae87 to 8a96c9c Compare June 24, 2026 20:35

NiteshDhanpal approved these changes Jun 24, 2026

View reviewed changes

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch 3 times, most recently from c652fd6 to 056936e Compare June 25, 2026 15:52

greptile-apps Bot reviewed Jun 25, 2026

View reviewed changes

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch 4 times, most recently from 34b20d7 to c033407 Compare July 1, 2026 20:12

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch 9 times, most recently from 991a96a to 851a14d Compare July 10, 2026 16:54

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch 9 times, most recently from 2a1af4a to 0bb8797 Compare August 4, 2026 15:12

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch 13 times, most recently from f3a521f to 520e23b Compare August 10, 2026 22:45

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch 5 times, most recently from f213fc7 to a133b22 Compare August 19, 2026 00:28

github-actions Bot force-pushed the release-please--branches--main--components--agentex branch 2 times, most recently from d8303c6 to 3e24522 Compare August 25, 2026 18:58

chore(main): release 0.2.0

ba37f51

Navigation Menu

Uh oh!

chore(main): release 0.2.0 - #326

chore(main): release 0.2.0#326
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--agentex

github-actions Bot commented Jun 19, 2026 •

edited by greptile-apps Bot

Loading

Uh oh!

greptile-apps Bot Jun 22, 2026

Uh oh!

Uh oh!

github-actions Bot commented Jun 24, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot Jun 25, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

github-actions Bot commented Jun 19, 2026 • edited by greptile-apps Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 I have created a release beep boop

0.2.0 (2026-09-15)

Features

Bug Fixes

Documentation

Refactors

Confidence Score: 4/5

Findings

Summary

Diagram

Uh oh!

greptile-apps Bot Jun 22, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✱ Stainless preview builds

Uh oh!

greptile-apps Bot Jun 25, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

github-actions Bot commented Jun 19, 2026 •

edited by greptile-apps Bot

Loading

github-actions Bot commented Jun 24, 2026 •

edited

Loading