Skip to content

Commit

Permalink
rel: prepare v2.4.3 (#1029)
Browse files Browse the repository at this point in the history
## Which problem is this PR solving?

- Releasing #1019

## Short description of the changes

- update CHANGELOG and RELEASE_NOTES
- no documentation updates
- no dependency license changes
  • Loading branch information
robbkidd authored Mar 1, 2024
1 parent 25a474e commit f56f63c
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 0 deletions.
9 changes: 9 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
# Refinery Changelog

## 2.4.3 2024-03-01

A bug fix release for a regression introduced in the 2.4.2 bug fix release.
It was possible to trigger 500 errors in Refinery's OTLP error responses when sending traces in an unsupported content-type.

### Fixes

- fix: upgrade husky to handle and add tests for invalid content type errors (#1019) | [Mike Goldsmith](https://github.com/MikeGoldsmith) & [Robb Kidd](https://github.com/robbkidd)

## 2.4.2 2024-02-28

This is a bug fix release for returning a improperly formatted OTLP error responses.
Expand Down
6 changes: 6 additions & 0 deletions RELEASE_NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,12 @@

While [CHANGELOG.md](./CHANGELOG.md) contains detailed documentation and links to all the source code changes in a given release, this document is intended to be aimed at a more comprehensible version of the contents of the release from the point of view of users of Refinery.

## Version 2.4.3

A bug fix release for a regression introduced in the 2.4.2 bug fix release.
It was possible to trigger 500 errors in Refinery's OTLP error responses when sending traces in an unsupported content-type.
This release is a recommended upgrade for anyone sending OTLP data to Refinery.

## Version 2.4.2

This is a bug fix release for returning a improperly formatted OTLP error responses.
Expand Down

0 comments on commit f56f63c

Please sign in to comment.