Repository navigation
Keep registry pipelines healthy when individual plugins break - #1594
Merged
Merged
Conversation
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.
A broken plugin now gets skipped during registry-wide validation and publication while healthy plugins continue. Changed-record PR reviews remain strict.
A rewritten repository history left a reviewed commit unreachable, causing main validation to fail despite publication already skipping that plugin. This applies isolation consistently to artifact failures, malformed records, unreadable overviews, duplicate sources, and references to skipped featured entries. Pending proposals remain unpublished and no longer block approved entries.
Verification: 189 tests pass, including failing-first CLI regressions for malformed records, unreadable overviews, source failures, and publication output. Full local online validation and publication each resolved 433 plugins and skipped only Prometheus Status at its unreachable reviewed pin. All generated index/detail entries and artifact pins match their source records; featured IDs remain valid.
Risk surface: registry loading and publication eligibility. Regressions cover strict review behavior and the empty-result safeguard. No plugin pins change.