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
07c161b to
e4fa035
Compare
5ea8b57 to
e9f8adc
Compare
520e23b to
ccb49b1
Compare
ccb49b1 to
a2432e2
Compare
1 participant
🤖 I have created a release beep boop
0.2.0 (2026-08-13)
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 a Release Please–generated PR that bumps the workspace to v0.2.0, collecting ~25 features and ~30 bug fixes accumulated since v0.1.0. All six changed files are version-metadata only —
pyproject.tomlfiles,_version.py,openapi.yaml,.release-please-manifest.json, and the newCHANGELOG.md.0.2.0across all four files that carry them (agentex/pyproject.toml, rootpyproject.toml,agentex/src/_version.py,agentex/openapi.yaml).CHANGELOG.mdis created for the first time and accurately reflects the commits included in this release (Slack/Linear gateways, OIDC delegation, schedules, retention improvements, and numerous CVE-clearing dependency bumps).Confidence Score: 5/5
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Feature PRs merged to main\n#329 #332 #335 #350 #351 etc.] --> B[Release Please detects\nconventional commits] B --> C[Generates release PR #326\nchore: release 0.2.0] C --> D{Version bumps} D --> E[.release-please-manifest.json\n0.1.0 → 0.2.0] D --> F[pyproject.toml root\n0.1.0 → 0.2.0] D --> G[agentex/pyproject.toml\n0.1.0 → 0.2.0] D --> H[agentex/src/_version.py\n0.1.0 → 0.2.0] D --> I[agentex/openapi.yaml\nversion: 0.2.0] C --> J[Generates CHANGELOG.md\nwith all 0.2.0 entries] E & F & G & H & I & J --> K[PR merged → GitHub Release\nv0.2.0 tag created] K --> L[Docker image built &\npushed with tag 0.2.0]Reviews (63): Last reviewed commit: "chore(main): release 0.2.0" | Re-trigger Greptile