Fix legacy incident component attachment - #414
Merged
Merged
Conversation
jbrooksuk
force-pushed
the
codex/fix-incident-component-attachment
branch
from
August 5, 2026 09:11
f0a768e to
dc119b8
Compare
jbrooksuk
marked this pull request as ready for review
August 5, 2026 09:11
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
1 participant
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
component_id/component_statuspayload to the incident's component pivotRoot cause
The create action validated the legacy fields but only synchronized components supplied through the
componentsarray, leaving the legacy component unattached.Closes cachethq/cachet#4611
Validation
vendor/bin/pest tests/Feature/Api/IncidentTest.phpvendor/bin/pint --dirtyvendor/bin/phpstan analyse --memory-limit=1G