Release v0.3.3#220
Merged
Merged
Conversation
…erated workflows (#218) * chore(deps): pin Azure SDK majors and stamp AgentOps version into generated workflows Two complementary changes that make CI runs reproducible and prevent the class of failure that produced the v0.3.2 stage regression (azure-ai-projects 1.x -> 2.x silently broke prompt-agent staging during a live tutorial recording). pyproject.toml - Add <X.0 upper bounds to every Azure SDK dependency (azure-ai-projects, azure-ai-evaluation, azure-identity, azure-monitor-*, azure-mgmt-*) plus pandas, fastapi, uvicorn, httpx, markdown. cryptography is intentionally left unbounded so security patches flow through. services/cicd.py + 20 template files - New helper _agentops_install_spec() maps the installed agentops version to a pip spec: clean public release -> "==X.Y.Z"; editable/dev install -> the existing " @ git+...@main" fallback. PEP 440 aware via packaging.Version. - New __AGENTOPS_INSTALL_SPEC__ template substitution wired into generate_cicd_workflows. - All 10 GitHub Actions workflow templates AND all 10 Azure DevOps pipeline templates rewritten to use __AGENTOPS_INSTALL_SPEC__ in place of the hardcoded "@ git+https://github.com/Azure/agentops.git@main" suffix. - Stale "NOTE: pinned to GitHub main until the next package release" comments removed from 5 templates (the note no longer applies once the install line carries a real version pin). tests/unit/test_cicd.py - 5 new tests cover: clean release -> ==X.Y.Z; PEP 440 post/rc releases -> pin; dev/local segments -> @main fallback; rendered workflows pin to the substituted version end-to-end; dev installs still write the @main fallback into the rendered template. Net effect: a user who runs `agentops workflow generate` against AgentOps 0.3.3 gets workflow files that always install `agentops-accelerator==0.3.3` on every CI run, and `agentops-accelerator` pins the right Azure SDK majors via the new upper bounds. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(cicd): satisfy mypy str|None narrowing in _agentops_install_spec Use an explicit esolved: str local instead of shadowing the parameter via rom agentops import __version__ as version. mypy 1.x couldn't narrow str | None -> str through the import-rebind, producing 'Argument 1 to `Version` has incompatible type `str | None`'. No behavior change; tests/unit/test_cicd.py still 66/66 green. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(cli): satisfy mypy type-narrowing in run_wizard on_answer callback mypy 1.x cannot narrow the type of a kwargs spread built from a single-field dict literal — it eagerly assumes the value matches the *first* WizardAnswers field's type (Path | None), producing 'Argument 1 to `WizardAnswers` has incompatible type `**dict[str, str]`'. Materialize the partial dict as `dict[str, Any]` so the spread satisfies every field type. Pre-existing failure on develop — unblocking lint for this PR. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
… regression false-positive) (#219) Three coordinated schema-alignment fixes to agent/sources/results_history.py: 1. _summarize reads top-level aggregate_metrics (the field core/results.py actually writes), falling back to legacy metrics/run_metrics. 2. _summarize prefers summary.overall_passed for run_pass, falling back to legacy shapes. 3. _summarize orders runs by finished_at/started_at (the fields results.json actually contains), not just the legacy timestamp list. 4. _collect_local_runs now includes .agentops/results/latest/ when it is the only local results directory. In CI, generated workflows write only to that path (per services/cicd.py:28 _CI_EVAL_OUTPUT), so excluding it left local_runs empty and the regression check fell back on the stale Foundry cloud listing - flagging the previous PR's run as if it were current. Adds 4 unit tests covering CI mode, dev-mode dedup, the metrics field, and finished_at ordering. Full suite: 817 passed, 1 skipped. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v0.3.3
Automated release branch created from
develop.What happened
release/v0.3.3created fromdevelopCHANGELOG.mdupdated: versioned section[0.3.3]added0.3.3(package.json, plugin.json, marketplace.json)Next steps
maingit tag v0.3.3 && git push origin v0.3.3git checkout develop && git merge main && git push origin developChecklist
v0.3.3pushed