[release] v0.100.8#4494
Merged
Merged
Conversation
Previously RetrievalInfo lived under api/oss/src/apis/fastapi/git/ and the routers assembled it directly, including making duplicate environment-revision DB calls to gather environment-side references. This commit moves the DTO and helpers to api/oss/src/core/git/ for symmetry with ResolutionInfo, threads retrieval_info through the services as the third element of a (revision, resolution_info, retrieval_info) tuple, and lets the routers act as pass-throughs. Highlights: - core/git/dtos.py: RetrievalInfo Pydantic model - core/git/utils.py: build_retrieval_info / revision_references helpers - Six services updated to return the 3-tuple; environment-backed paths merge environment + target references inside the service, no router-level DB call - Queries and testsets gain thin retrieve_*_revision wrappers for symmetry - /revisions/retrieve and /revisions/resolve responses carry retrieval_info - Unit + acceptance test coverage for all six entities, both retrieve and resolve, direct and environment-backed No request-field renames in this commit; only the internal refactor and the new retrieval_info on retrieve/resolve responses.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Resolved conflicts by keeping both import sets (RetrievalInfo/build_retrieval_info from HEAD and validate_* functions from incoming) across all service and router files. In environments/service.py, adopted the incoming simplification of retrieve_environment_revision to delegate to fetch_environment_revision (which includes the full validation set), restored build_retrieval_info call and fixed the incorrect 2-tuple return to 3-tuple. In the SDK test file, kept HEAD's test_stores_retrieval_references_on_tracing_context method and appended the incoming TestResolverMiddlewareTracingParameters class. Dropped unused VariantForkError import from all three routers (now handled by handle_git_exceptions). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Removes APPLICATIONS_REVISIONS_* and EVALUATORS_REVISIONS_* from EventType and WebhookEventType (applications/evaluators now emit as workflow events). Adds two defensive guards so existing stored data with the old string values doesn't cause runtime errors: - mappings.py: fall back to EventType.UNKNOWN for unrecognized DB rows - webhooks/types.py: drop unknown event_type strings from subscription data instead of raising a validation error on load Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The coercion belongs at the type boundary, not the mapping function. Any code path constructing an Event from a raw string now gets the fallback to UNKNOWN automatically. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… order - QuickDateRangePicker: store relative presets with `to: null` so the audit-log window stays live to "now", matching the default range and the Refresh action. A fixed upper bound captured at selection time was hiding events created after the preset was picked until a manual refresh. - EventQuery generated type: reorder fields to match the backend model definition so a future Fern client regen produces a no-op diff instead of diverging.
…ow-events [fix] Resolve broken events and audit log
Contributor
Author
Railway Preview Environment
Updated at 2026-05-31T14:50:19.028Z |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
[fix] Resolve broken os organization slug
…i-and-sdk [feat] Resolve broken references in traces
…m:Agenta-AI/agenta into release/v0.100.8
junaway
approved these changes
May 31, 2026
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
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.
New version v0.100.8 in