Model Upgrade: gpt-4o-2024-11-20 → gpt-4.1#3
Merged
Conversation
Contributor
✅ Agent Deployment & Evaluation Report🤖 Agent Details
📊 Pipeline Results
🛠️ Tools Configuration
🔗 Links🤖 Updated automatically by the CI pipeline · 2026-05-15 19:54:45 UTC |
Strip newlines from output preview before writing to GITHUB_OUTPUT, as multiline values break the key=value format.
Replace microsoft/ai-agent-evals action with custom run_evaluation.py
that creates one evaluation per agent and adds runs on each pipeline
execution. Run names encode branch/commit for traceability.
- First run: creates evaluation named '{agent-name}-eval'
- Subsequent runs: reuses existing evaluation, adds new run
- Run name format: '{branch}/{commit-sha}'
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.
Summary
gpt-4o-2024-11-20togpt-4.1GPT_DEPLOYMENTupdated togpt-4.1Why this needs an eval gate
Swapping models is a behaviour change. The new model may:
The eval workflow will deploy with the new model and verify all scores
meet thresholds before this can be merged.
Changes
agents/tech-trends-agent.json_model_historyannotationGPT_DEPLOYMENTgpt-4o-2024-11-20→gpt-4.1What to check
Phase
Phase 3 of 3 — model upgrade. Lifecycle demo complete after merge.