Skip to content

Replace obsolete unprocessable_entity with unprocessable_content - #1085

Merged
FerPerales merged 1 commit into
thoughtbot:mainfrom
sej3506:update-obsolete-http-status-code
Mar 12, 2026
Merged

FerPerales merged 1 commit into
thoughtbot:mainfrom
sej3506:update-obsolete-http-status-code

Conversation

@sej3506

@sej3506 sej3506 commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

This change replaces all instances of :unprocessable_entity with :unprocessable_content.

In keeping aligned with the IANA HTTP Status Code Registry, Rack deprecated unprocessable_entity for unprocessable_content. They still include handling for the time being but have included a deprecation notice.

More info: rack/rack#2137

This change replaces all instances of :unprocessable_entity with
:unprocessable_content.

In keeping aligned with the IANA HTTP Status Code Registry, Rack
deprecated unprocessable_entity for unprocessable_content. They still
include handling for the time being but have included a deprecation
notice.

More info: rack/rack#2137
@sej3506
sej3506 requested a review from FerPerales as a code owner March 2, 2026 16:16

@FerPerales FerPerales left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! @sej3506

Do we need to upgrade rake/rails as well? 🤔

@sej3506

sej3506 commented Mar 3, 2026

Copy link
Copy Markdown
Contributor Author

@FerPerales We wouldn't need to at this time. The changes have been live in rack since at least 2024 and we've been getting the deprication warning in our tests on CI, too. Example.

@FerPerales
FerPerales merged commit c76ac6d into thoughtbot:main Mar 12, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants