Skip to content

fix(audits/server): JSON parsing errors format shouldnt be audited #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Jan 20, 2023
Merged

fix(audits/server): JSON parsing errors format shouldnt be audited #47

merged 2 commits into from
Jan 20, 2023

Conversation

@enisdenjo
Copy link
Member

@enisdenjo enisdenjo commented Jan 20, 2023

Closes #25

@enisdenjo enisdenjo mentioned this pull request Jan 20, 2023
Closed
@enisdenjo enisdenjo merged commit fae7e59 into main Jan 20, 2023
@enisdenjo enisdenjo deleted the json-parsing branch January 20, 2023 16:23
enisdenjo pushed a commit that referenced this pull request Jan 26, 2023
@semantic-release-bot
chore(release): 🎉 1.13.0 [skip ci]
d54b4fe 
# [1.13.0](v1.12.0...v1.13.0) (2023-01-26)

### Bug Fixes

* **audits/server:** JSON parsing errors format shouldnt be audited ([#47](#47)) ([fae7e59](fae7e59))

### Features

* **audits:** Every audit should have a globally unique ID ([#49](#49)) ([8f6d4f1](8f6d4f1))
@enisdenjo
Copy link
Member Author

enisdenjo commented Jan 26, 2023

🎉 This PR is included in version 1.13.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@enisdenjo enisdenjo added the released Has been released and published label Jan 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

released Has been released and published

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

SHOULD not contain the data entry on JSON parsing failure when accepting application/graphql-response+json also fails on non-JSON responses

2 participants

@enisdenjo