Repository navigation
ci: add shared digest candidate release workflow - #527
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
AI assistance
Codex prepared and validated the change under the repository owner's instruction.
What changed
Add a manual caller for the pinned organization release workflow. Production can verify the existing job image; deploy and rollback use a separate test environment. Cloud configuration is passed by name.
How verified
Actionlint, the documentation check and the staged diff check passed. The production Job configuration was inspected read-only. Isolated deployment and rollback are verified separately after merge.
Why
Reuse the GCP Job adapter for the non-trading digest producer and keep the producer schedule and runtime unchanged.
Risk
R2, GitHub release workflow only. Production is read-only, and the caller cannot invoke the job or change its schedule.