Skip to content

Commit f56f63c

Browse files
authored
rel: prepare v2.4.3 (#1029)
## 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
1 parent 25a474e commit f56f63c

File tree

2 files changed

+15
-0
lines changed

2 files changed

+15
-0
lines changed

CHANGELOG.md

+9
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,14 @@
11
# Refinery Changelog
22

3+
## 2.4.3 2024-03-01
4+
5+
A bug fix release for a regression introduced in the 2.4.2 bug fix release.
6+
It was possible to trigger 500 errors in Refinery's OTLP error responses when sending traces in an unsupported content-type.
7+
8+
### Fixes
9+
10+
- 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)
11+
312
## 2.4.2 2024-02-28
413

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

RELEASE_NOTES.md

+6
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,12 @@
22

33
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.
44

5+
## Version 2.4.3
6+
7+
A bug fix release for a regression introduced in the 2.4.2 bug fix release.
8+
It was possible to trigger 500 errors in Refinery's OTLP error responses when sending traces in an unsupported content-type.
9+
This release is a recommended upgrade for anyone sending OTLP data to Refinery.
10+
511
## Version 2.4.2
612

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

0 commit comments

Comments
 (0)