Milestone branch next, mergeable to main at every moment. It was recreated from main after #321 merged.
On the branch since main:
/s/* answers only GET and HEAD; other methods get 405 (#169).
In progress, landing here when reviewed: #340, the container setting its own data directory owner and mode before start. It is the priority for the upaas deploy.
This description is updated as units land. The 1.0 tag waits on your production run, separately from any merge.
Model: opus-5-5
Milestone branch `next`, mergeable to `main` at every moment. It was recreated from `main` after https://git.eeqj.de/sneak/webhooker/pulls/321 merged.
On the branch since `main`:
- `/s/*` answers only `GET` and `HEAD`; other methods get `405` (https://git.eeqj.de/sneak/webhooker/issues/169).
In progress, landing here when reviewed: https://git.eeqj.de/sneak/webhooker/issues/340, the container setting its own data directory owner and mode before start. It is the priority for the upaas deploy.
This description is updated as units land. The 1.0 tag waits on your production run, separately from any merge.
Model: opus-5-5
clawbot
self-assigned this 2026-09-29 11:10:51 +02:00
The static file server was attached with Mount, which registers every
method, so POST, PUT and DELETE on an asset were answered 200 with the
file. It is now registered for GET and HEAD only, inside a /s group
whose method-not-allowed handler answers 405 with Allow: GET, HEAD.
A method chi does not route at all, such as PROPFIND, still gets 405
from the top-level router, without Allow. The inverted test and the
README route table say the same.
Model: opus-5-5
sneak
merged commit a891b726e5 into main2026-09-29 11:53:19 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Milestone branch
next, mergeable tomainat every moment. It was recreated frommainafter #321 merged.On the branch since
main:/s/*answers onlyGETandHEAD; other methods get405(#169).In progress, landing here when reviewed: #340, the container setting its own data directory owner and mode before start. It is the priority for the upaas deploy.
This description is updated as units land. The 1.0 tag waits on your production run, separately from any merge.
Model: opus-5-5