Skip to content

Commit d5fda18

Browse files
docs(vllm-omni): apply flowmark 150-col wrapping
1 parent efdc5b9 commit d5fda18

2 files changed

Lines changed: 6 additions & 6 deletions

File tree

docs/vllm-omni/changelog/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ Changelog for the Amazon Linux 2023-based vLLM-Omni images (`omni-cuda`, `omni-s
1414

1515
### Changes
1616

17-
- **SageMaker `/v1/videos` and `/v1/videos/sync` now accept `application/json` again.** The routing middleware restores JSON→multipart
18-
conversion for the form-data video routes, so clients can send a plain JSON body instead of hand-building multipart. The existing
19-
`multipart/form-data` path is unchanged (byte-for-byte passthrough), so callers already sending multipart need no changes.
17+
- **SageMaker `/v1/videos` and `/v1/videos/sync` now accept `application/json` again.** The routing middleware restores JSON→multipart conversion for
18+
the form-data video routes, so clients can send a plain JSON body instead of hand-building multipart. The existing `multipart/form-data` path is
19+
unchanged (byte-for-byte passthrough), so callers already sending multipart need no changes.
2020

2121
### Notes
2222

docs/vllm-omni/deployment/sagemaker.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,9 +67,9 @@ response = predictor.predict(
6767
)
6868
```
6969

70-
The `/v1/videos` and `/v1/videos/sync` routes accept either `application/json` or `multipart/form-data`. As of `omni-sagemaker-cuda-v1.4`, the
71-
routing middleware again converts a JSON body to multipart for these routes (this was disabled in `v1.2` and restored in `v1.4`), so sending JSON —
72-
as in the image and chat examples above — works. The `multipart/form-data` path below is still supported unchanged and remains useful when you want
70+
The `/v1/videos` and `/v1/videos/sync` routes accept either `application/json` or `multipart/form-data`. As of `omni-sagemaker-cuda-v1.4`, the routing
71+
middleware again converts a JSON body to multipart for these routes (this was disabled in `v1.2` and restored in `v1.4`), so sending JSON — as in the
72+
image and chat examples above — works. The `multipart/form-data` path below is still supported unchanged and remains useful when you want
7373
byte-for-byte control over the request body.
7474

7575
```python

0 commit comments

Comments
 (0)