chore(main): release 0.2.0 - #326
Conversation
63c1abc to
34c3cdd
Compare
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| [project] | ||
| name = "agentex" | ||
| version = "0.1.0" | ||
| version = "0.1.1" |
There was a problem hiding this comment.
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.
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
Bot
changed the title
e158b69 to
d1cae87
Compare
✱ Stainless preview buildsThis PR will update the openapi python typescript Edit this comment to update them. They will appear in their respective SDK's changelogs. ✅ agentex-sdk-openapi studio · code · diff
✅ agentex-sdk-typescript studio · code · diff
⚡ agentex-sdk-python studio · conflict
This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push. |
d1cae87 to
8a96c9c
Compare
c652fd6 to
056936e
Compare
| [project] | ||
| name = "agentex" | ||
| version = "0.1.0" | ||
| version = "0.2.0" |
There was a problem hiding this comment.
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.
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.
34b20d7 to
c033407
Compare
991a96a to
851a14d
Compare
72e1bb3 to
d408ede
Compare
f49d00a to
f3a521f
Compare
a2432e2 to
94950ea
Compare
94950ea to
f213fc7
Compare
1 participant
🤖 I have created a release beep boop
0.2.0 (2026-08-14)
Features
Authorization: AgentKeyon forward routes (#402) (dbd5b2c)Bug Fixes
paramsfrom the list-tasks response (#377) (e62a2a7)Documentation
Refactors
This PR was generated with Release Please. See documentation.
Greptile Summary
This is an automated Release Please PR bumping the agentex workspace from v0.1.0 to v0.2.0. All six changed files are version string updates and a generated CHANGELOG — no logic is modified.
.release-please-manifest.json,agentex/pyproject.toml,pyproject.toml,agentex/openapi.yaml, andagentex/src/_version.pyall move from0.1.0→0.2.0.Confidence Score: 5/5
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD RP[Release Please Bot] -->|bumps version strings| MF[.release-please-manifest.json\n0.1.0 → 0.2.0] RP -->|generates| CL[CHANGELOG.md\nv0.2.0 entries] RP -->|bumps| PY1[pyproject.toml\nagentex 0.2.0] RP -->|bumps| PY2[agentex/pyproject.toml\nagentex-backend 0.2.0] RP -->|bumps| VER[agentex/src/_version.py\n__version__ = 0.2.0] RP -->|bumps| OA[agentex/openapi.yaml\ninfo.version: 0.2.0] MF & PY1 & PY2 & VER & OA --> TAG[Git tag: v0.2.0]Reviews (65): Last reviewed commit: "chore(main): release 0.2.0" | Re-trigger Greptile