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.| """Single source of the agentex contract version (bumped by release-please).""" | ||
|
|
||
| __version__ = "0.1.0" # x-release-please-version | ||
| __version__ = "0.2.0" # x-release-please-version |
There was a problem hiding this comment.
The API version now comes from __version__ and is 0.2.0, but src/utils/otel_metrics.py still falls back to SERVICE_VERSION 0.1.0 and get_meter(..., version="0.1.0"). Internal callers use get_meter without passing a version, so deployments that do not set SERVICE_VERSION emit 0.2.0 service metrics under the old 0.1.0 version, which can make rollout dashboards and version comparisons incorrect.
Artifacts
Repro: Python harness that exercises telemetry version defaults with SERVICE_VERSION unset
- Contains supporting evidence from the run (text/x-python; charset=utf-8).
Repro: harness output showing package version 0.2.0 but telemetry resource and meter version 0.1.0
- 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: agentex/src/_version.py
Line: 3
Comment:
**Update telemetry version defaults**
The API version now comes from `__version__` and is `0.2.0`, but `src/utils/otel_metrics.py` still falls back to `SERVICE_VERSION` `0.1.0` and `get_meter(..., version="0.1.0")`. Internal callers use `get_meter` without passing a version, so deployments that do not set `SERVICE_VERSION` emit 0.2.0 service metrics under the old 0.1.0 version, which can make rollout dashboards and version comparisons incorrect.
How can I resolve this? If you propose a fix, please make it concise.
34b20d7 to
c033407
Compare
991a96a to
851a14d
Compare
4d9c828 to
7cf8e85
Compare
1cbcbb4 to
ad182c7
Compare
10d4f46 to
fa0dddf
Compare
fa0dddf to
2a1af4a
Compare
1 participant
🤖 I have created a release beep boop
0.2.0 (2026-08-04)
Features
Bug Fixes
paramsfrom the list-tasks response (#377) (e62a2a7)Documentation
This PR was generated with Release Please. See documentation.
Greptile Summary
This is a release-please generated PR that bumps all workspace packages from
0.1.0to0.2.0, createsCHANGELOG.md, and regeneratesagentex/openapi.yamlwith the new version and reformatted YAML indentation. No functional code changes are introduced — all feature and bug-fix commits were merged separately.agentex/src/_version.py,agentex/pyproject.toml,pyproject.toml, and.release-please-manifest.jsonall updated to0.2.0.v0.1.0.info.versionupdated to0.2.0; YAML parameter blocks reformatted from 2-space to 4-space indentation and longoperationIdvalues wrapped as block scalars — no schema changes.Confidence Score: 5/5
Safe to merge — all changes are automated release-please version bumps and a generated CHANGELOG with no functional code modifications.
All six changed files are release-please output: version strings, the manifest, a new CHANGELOG, and a regenerated OpenAPI spec with only a version bump and YAML reformatting. No logic, no migrations, no auth paths are touched.
Files Needing Attention: No files require special attention.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[release-please bot] --> B[Bump .release-please-manifest.json\n0.1.0 → 0.2.0] A --> C[Create CHANGELOG.md\n15 features · 22 fixes · 3 docs] A --> D[Bump pyproject.toml\nagentex workspace 0.2.0] A --> E[Bump agentex/pyproject.toml\nagentex-backend 0.2.0] A --> F[Bump agentex/src/_version.py\n__version__ = 0.2.0] A --> G[Regenerate agentex/openapi.yaml\ninfo.version 0.2.0 + YAML reformat] B & C & D & E & F & G --> H[PR #326 merged → v0.2.0 tag]Reviews (47): Last reviewed commit: "chore(main): release 0.2.0" | Re-trigger Greptile