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
f706767 to
fd9cecf
Compare
fd9cecf to
4d9c828
Compare
1 participant
🤖 I have created a release beep boop
0.2.0 (2026-07-16)
Features
Bug Fixes
Documentation
This PR was generated with Release Please. See documentation.
Greptile Summary
This is an auto-generated release PR from release-please, bumping the project from v0.1.0 to v0.2.0. It creates
CHANGELOG.md, updates the version in.release-please-manifest.json, bothpyproject.tomlfiles,agentex/src/_version.py, and regeneratesagentex/openapi.yamlwith the new API version plus all endpoint additions that landed since v0.1.0 (agent run schedules, webhook trigger setup, OIDC bearer delegation, task interrupts, and related bug fixes).0.2.0across all five touched version files.agentex/openapi.yamlis reformatted for consistent indentation and extended with new paths for schedules (CRUD, trigger, skip/unskip, pause/resume), webhook API-key setup, and theINTERRUPTEDtask status.aiohttp>=3.14.1,ddtrace>=4.8.2,fastapi<0.137.0, etc.) are reflected inagentex/pyproject.tomland the workspace override block in the rootpyproject.toml.Confidence Score: 5/5
Release-only PR — all six changed files are version strings, a generated changelog, and a regenerated OpenAPI spec. No logic changes are introduced here.
Every version file is consistently updated to 0.2.0, dependency floor comments match the pinned ranges, and the openapi.yaml additions faithfully reflect the endpoints that shipped in the constituent PRs. There are no code-logic changes in this PR.
No files require special attention.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[release-please bot detects merged PRs] --> B[Bump version 0.1.0 → 0.2.0] B --> C1[.release-please-manifest.json] B --> C2[pyproject.toml root] B --> C3[agentex/pyproject.toml] B --> C4[agentex/src/_version.py] B --> C5[agentex/openapi.yaml info.version] B --> C6[CHANGELOG.md created] C1 & C2 & C3 & C4 & C5 & C6 --> D[PR #326 merged to main] D --> E[GitHub Release tag v0.2.0] E --> F[Docker build: uv sync --frozen agentex-backend] F --> G{uv.lock up-to-date?} G -->|Yes| H[Image built successfully] G -->|No — still records 0.1.0| I[Frozen lock check may fail]%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%% flowchart TD A[release-please bot detects merged PRs] --> B[Bump version 0.1.0 → 0.2.0] B --> C1[.release-please-manifest.json] B --> C2[pyproject.toml root] B --> C3[agentex/pyproject.toml] B --> C4[agentex/src/_version.py] B --> C5[agentex/openapi.yaml info.version] B --> C6[CHANGELOG.md created] C1 & C2 & C3 & C4 & C5 & C6 --> D[PR #326 merged to main] D --> E[GitHub Release tag v0.2.0] E --> F[Docker build: uv sync --frozen agentex-backend] F --> G{uv.lock up-to-date?} G -->|Yes| H[Image built successfully] G -->|No — still records 0.1.0| I[Frozen lock check may fail]Reviews (31): Last reviewed commit: "chore(main): release 0.2.0" | Re-trigger Greptile