Skip to content

fix(action): ensure valid JSON output by using unique delimiter for multiline outputs#485

Open
zagers wants to merge 1 commit intogoogle-github-actions:mainfrom
zagers:bug/summary-output-field-contains-invalid-JSON
Open

fix(action): ensure valid JSON output by using unique delimiter for multiline outputs#485
zagers wants to merge 1 commit intogoogle-github-actions:mainfrom
zagers:bug/summary-output-field-contains-invalid-JSON

Conversation

@zagers
Copy link

@zagers zagers commented Mar 22, 2026

Fixes a bug where the 'gemini_response' and 'gemini_errors' output fields contained extra characters when using JSON output format. By using a more unique delimiter and grouping the commands, we ensure the redirection to GITHUB_OUTPUT is correctly terminated.

Closes #381

…ultiline outputs

Fixes a bug where the 'gemini_response' and 'gemini_errors' output fields
contained extra characters when using JSON output format. By using a more
unique delimiter and grouping the commands, we ensure the redirection to
GITHUB_OUTPUT is correctly terminated.

Closes google-github-actions#381
@zagers zagers requested review from a team as code owners March 22, 2026 13:58
@google-cla
Copy link

google-cla bot commented Mar 22, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Summary output field contains invalid JSON when using json output format

1 participant