Repository navigation
fix: isolate candidate roots without moving notification markers - #492
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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 (GPT-6), with local self-review.
What changed
A private per-target binding can override the heartbeat workflow's candidate URI, leaving writers on an old bucket after a migration. Add the explicit repository variable
DIGEST_CANDIDATES_OVERRIDE_GCS_URI, applied after binding resolution. Preserve the original explicit marker root, or its former candidate-root default, so existing incident reservations remain authoritative.The default remains unchanged. Invalid override roots fail before storage access. Target identity, archive inputs, enablement, trading paths, and central delivery receipts are unchanged. Document single-target configuration and staged migration.
How verified