Repository navigation
Refs #39586 - Avoid double encoding for JSON reports (5.0-stable) - #11350
Merged
ofedoren merged 1 commit intoOct 23, 2026
Merged
Conversation
(cherry picked from commit 4dd9610)
pr-processor
Bot
added
Not yet reviewed
Stable branch
ofedoren
approved these changes
Oct 22, 2026
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.
Summary
Cherry-pick Foreman develop commit 4dd9610 to
5.0-stablewith-x. Prevent double encoding of JSON report output, with its controller regression test. This is present downstream but missing upstream stable.Testing
git diff --checkandruby -con the changed controller and test pass.bundle checkreports missing dependencies. Please validate in upstream PR CI.