✨ Add hierarchical group parents in 0.9.3 - #697
Merged
Merged
Conversation
✨ Add OAuth refresh workflow
🐛 Support Helm 4 workflow qualification
♻️ Organize agent-service database adapters
jrosseel
added a commit
that referenced
this pull request
Aug 24, 2026
🐛 Repair CI guard migrations after #697
This was referenced Aug 24, 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.
Summary
Merge order
This PR must merge last. Its branch contains the complete heads of #696 and #698, so those PRs are superseded by this review surface and will be closed after this PR is green.
Validation
Live qualification
After GitHub CI is green, the exact PR head will be deployed to the disposable testv4 cluster and the authenticated HTTP/WebSocket journey will be qualified there.
Local limitation
The workstation has no Docker daemon, so the PostgreSQL convergence proof runs in CI and during the testv4 deployment rather than locally.