Skip to content

Commit 5586bf0

Browse files
[autofix.ci] apply automated fixes
1 parent e88c2eb commit 5586bf0

1 file changed

Lines changed: 10 additions & 5 deletions

File tree

‎docs/source/changelog/2026.10.09.md‎

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,14 @@
22

33
## Changes
44

5-
- Cover server errors from synchronous and asynchronous cloud recognition queries. ([#3214](https://github.com/VWS-Python/vws-python/issues/3214))
6-
- Model test credentials as pairs and name OAuth endpoint metadata precisely, avoiding secret false positives. ([#3215](https://github.com/VWS-Python/vws-python/issues/3215))
7-
- Remove supported inline type-checking comments by teaching Ruff about runtime-evaluated `beartype` annotations and postponing test annotations. ([#3216](https://github.com/VWS-Python/vws-python/issues/3216))
8-
- Validate query and Model Target report response values at construction time. ([#3218](https://github.com/VWS-Python/vws-python/issues/3218))
9-
- Type decoded report response dictionaries as JSON values. ([#3223](https://github.com/VWS-Python/vws-python/issues/3223))
5+
- Cover server errors from synchronous and asynchronous cloud recognition queries.
6+
([#3214](https://github.com/VWS-Python/vws-python/issues/3214))
7+
- Model test credentials as pairs and name OAuth endpoint metadata precisely, avoiding secret false positives.
8+
([#3215](https://github.com/VWS-Python/vws-python/issues/3215))
9+
- Remove supported inline type-checking comments by teaching Ruff about runtime-evaluated `beartype` annotations and postponing test annotations.
10+
([#3216](https://github.com/VWS-Python/vws-python/issues/3216))
11+
- Validate query and Model Target report response values at construction time.
12+
([#3218](https://github.com/VWS-Python/vws-python/issues/3218))
13+
- Type decoded report response dictionaries as JSON values.
14+
([#3223](https://github.com/VWS-Python/vws-python/issues/3223))
1015
- Publish native Markdown release notes and use the same notes in documentation where available.

0 commit comments

Comments
 (0)