Repository navigation
Prevent duplicate compatibility release PRs - #44
Merged
Merged
Conversation
A release merge changes the discovery SHA even when the tested code and Plex inputs are unchanged. Recognize authenticated published equivalents before creating another report or staged version. Confidence: high Scope-risk: moderate Directive: Never ignore runtime, workflow, script or fixture changes Tested: 116 Python tests, actionlint, diff checks Not-tested: Updated monitor on GitHub runners
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.
The compatibility bot created duplicate release PRs after the v1.3.23 merge because the discovery source SHA changed. It now checks the latest regular release, authenticated certification evidence, exact Plex profiles, published asset hashes and executable source tree before creating another report or release candidate. Only release prose may differ; runtime, workflow, script and fixture changes still require new certification.
README and changelog now describe the completed v1.3.23 tests and available downloads.
Validation: 116 Python tests, actionlint and diff checks passed. Regression tests cover newer releases, actual certificate authentication and rejected source/profile/asset/timestamp changes. The updated monitor still needs GitHub runner validation.