Skip to content

Put the 0.8.1 changelog entry in the maintained changelog #23

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

Merged
loookashow merged 1 commit into from
Sep 9, 2026
+4 −4
Merged

Put the 0.8.1 changelog entry in the maintained changelog #23

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Fixed

- `data_validation_error` (HTTP 422) now raises `ContentValidationFailed` instead of a bare `FoxnoseAPIError`. This is the code a Flux resource write returns for a schema violation, so the most common way to hit one was not caught by `except ContentValidationFailed`, and callers had to match on `status_code == 422` instead. The `errors` list and `errors_truncated` flag are populated from the same detail payload as `content_validation_failed`, and `error_code` still reports what the server sent.

## [0.6.0] - 2026-07-16

### Added
Expand Down
4 changes: 4 additions & 0 deletions docs/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Fixed

- `data_validation_error` (HTTP 422) now raises `ContentValidationFailed` instead of a bare `FoxnoseAPIError`. This is the code a Flux resource write returns for a schema violation, so the most common way to hit one was not caught by `except ContentValidationFailed`, and callers had to match on `status_code == 422` instead. The `errors` list and `errors_truncated` flag are populated from the same detail payload as `content_validation_failed`, and `error_code` still reports what the server sent.

## [0.8.0] - 2026-08-10

### Added
Expand Down
Loading