Skip to content
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.

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

Remove severity from error payload #277

Closed
amtins opened this issue Oct 21, 2024 · 1 comment · Fixed by #278
Closed

Remove severity from error payload #277

amtins opened this issue Oct 21, 2024 · 1 comment · Fixed by #278

Comments

@amtins
Copy link
Member

amtins commented Oct 21, 2024

As a developer I would like to remove warnings since we noticed they are not relevant.

Acceptance criteria

  • Warnings are not sent anymore
amtins added a commit that referenced this issue Oct 21, 2024
Resolves #277 by removing the severity property following the update of the
monitoring specification.
amtins added a commit that referenced this issue Oct 22, 2024
Resolves #277 by removing the severity property following the update of the
monitoring specification.
github-actions bot pushed a commit that referenced this issue Oct 22, 2024
## [1.14.1](v1.14.0...v1.14.1) (2024-10-22)

### Enhancements and Bug Fixes 🐛

* **pillarbox-monitoring:** remove severity property from error event ([614ed7f](614ed7f)), closes [#277](#277)
Copy link

🎉 This issue has been resolved in version 1.14.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant