Skip to content

latest and highest revision of revision groups via API, execute-highest - #293

Merged
stewit merged 1 commit into
developfrom
revision-group-latest-highest
Oct 8, 2026
Merged

stewit merged 1 commit into
developfrom
revision-group-latest-highest

Conversation

@stewit

@stewit stewit commented Oct 7, 2026

Copy link
Copy Markdown
Contributor
  • GET /api/transformations/revision_groups (+ /stubs) and /api/transformations/revision_groups/{revision_group_id} (+ /stub) return the latest (by release timestamp) or highest (by semantic versioning of the version tags) revision, chosen via query param by (default latest). Only released revisions by default, include_deprecated and, for highest, include_drafts extend this. The list endpoints filter like /transformations, the filters are applied first.
  • new endpoints execute-highest and execute-highest-async, Kafka execution messages accept "by": "highest"
  • the GET endpoints, execute-latest/-highest, Kafka and the upgrade operators button share one selection function, so they always agree on the selected revision. Ties of the release timestamp are broken by id.
  • Kafka executions of revision groups pass runtime_execution_context and resolved_reproducibility_references on, like the REST endpoints
  • docs, changelog and openapi.json updated

Assisted-by: Claude Code:claude-opus-5-5

- GET /api/transformations/revision_groups (+ /stubs) and
  /api/transformations/revision_groups/{revision_group_id} (+ /stub)
  return the latest (by release timestamp) or highest (by semantic
  versioning of the version tags) revision, chosen via query param `by`
  (default latest). Only released revisions by default, include_deprecated
  and, for highest, include_drafts extend this. The list endpoints filter
  like /transformations, the filters are applied first.
- new endpoints execute-highest and execute-highest-async, Kafka execution
  messages accept "by": "highest"
- the GET endpoints, execute-latest/-highest, Kafka and the upgrade
  operators button share one selection function, so they always agree on
  the selected revision. Ties of the release timestamp are broken by id.
- Kafka executions of revision groups pass runtime_execution_context and
  resolved_reproducibility_references on, like the REST endpoints
- docs, changelog and openapi.json updated

Assisted-by: Claude Code:claude-opus-5-5
@stewit
stewit merged commit 64877dd into develop Oct 8, 2026
3 checks passed
@stewit
stewit deleted the revision-group-latest-highest branch October 8, 2026 07:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant