[TODO] replace our Plugs.StaticNoC with upstream Plug.Static #734

New issue

Open

opened 2024-04-03 13:59:24 +00:00 by Oneric · 0 comments

Oneric commented

2024-04-03 13:59:24 +00:00

Member

Upstream merged the Content-Type opt-out from our vendored StaticNoC version; with plug’s next release we can thus move back to upstream.
Instead of a separate set_content_type option, it’s now part of the existing content_type mapping as the special value false.

If plug sticks to what appears to be their usual schedule of one minor release each year (often in October) followed by a few patch releases (which sometimes contain new additions) in the first couple months after, we might need to wait a while for 1.16.0. If we’re lucky we get a 1.15.4 with the setting earlier.

Upstream merged the `Content-Type` opt-out from our vendored `StaticNoC` version; with plug’s next release we can thus move back to upstream. Instead of a separate `set_content_type` option, it’s now part of the existing `content_type` mapping as the special value `false`. If plug sticks to what appears to be their usual schedule of one minor release each year (often in October) followed by a few patch releases *(which sometimes contain new additions)* in the first couple months after, we might need to wait a while for 1.16.0. If we’re lucky we get a 1.15.4 with the setting earlier.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#734

No description provided.