|
1 | 1 | # Changelog |
2 | 2 |
|
| 3 | +## 3.6.2 |
| 4 | + |
| 5 | +### Fixed: reject retired API credentials before use |
| 6 | + |
| 7 | +- The SDK rejects the retired API credential before storing or encoding it. |
| 8 | + |
| 9 | +### Fixed: full-scan reads wait for analysis to finish |
| 10 | + |
| 11 | +- `fullscans.stream()` now requests cached results (`?cached=true`) and polls |
| 12 | + while the API answers `202 Processing`, instead of treating the first `202` |
| 13 | + as a failed result. Polling backs off from 5s to 10s between attempts and |
| 14 | + stops when the budget runs out, raising `APITimeout`. |
| 15 | +- The polling budget defaults to the SDK's configured `timeout`. Callers can |
| 16 | + tune it with the new keyword-only arguments `poll_timeout_seconds`, |
| 17 | + `poll_initial_interval_seconds` and `poll_max_interval_seconds`. Each |
| 18 | + individual request is capped at 30 seconds or the remaining budget, |
| 19 | + whichever is shorter. |
| 20 | +- Transient failures (HTTP 408/502/503/504, timeouts, dropped connections) are |
| 21 | + retried within the budget. Authorization, not-found and quota errors still |
| 22 | + raise immediately. |
| 23 | +- Invalid polling settings (zero, negative, non-finite, booleans, or an |
| 24 | + initial interval above the maximum) raise `ValueError` before any request is |
| 25 | + sent. |
| 26 | +- The organization slug and full scan ID are now URL-encoded in the request |
| 27 | + path. |
| 28 | +- `API.do_request()` accepts an optional keyword-only `request_timeout` that |
| 29 | + overrides the configured timeout for a single call. |
| 30 | + |
| 31 | +## 3.6.1 |
| 32 | + |
| 33 | +### Security: patched releases of certifi, uv and virtualenv |
| 34 | + |
| 35 | +- Updated the locked versions of `certifi` (2025.11.12 → 2026.10.19), `uv` |
| 36 | + (0.11.17 → 0.13.4) and `virtualenv` (20.36.1 → 21.14.7) to pick up fixes for |
| 37 | + critical vulnerabilities. These versions are pinned in `uv.lock`, which |
| 38 | + controls the development and CI environment. |
| 39 | +- socketdev now requires `certifi>=2026.10.19`, so installing it also upgrades |
| 40 | + the CA bundle `requests` uses. Older bundles trust the compromised eMudhra |
| 41 | + intermediate CAs. |
| 42 | +- The release build toolchain (`.github/actions/setup-hatch`) now installs |
| 43 | + `virtualenv==21.14.7` and `hatchling==1.32.4`, matching `uv.lock` and the |
| 44 | + `[build-system]` pin. Published artifacts are built with the patched versions. |
| 45 | +- Raised the `requests` floor to `>=2.33.0`. |
| 46 | + |
| 47 | +### Changed: Python 3.10 or newer is required |
| 48 | + |
| 49 | +- `requires-python` is now `>=3.10` (previously `>=3.9`). The patched |
| 50 | + dependency releases no longer support Python 3.9, which reached end of life |
| 51 | + in October 2025. On Python 3.9, pip continues to resolve socketdev 3.6.0. |
| 52 | + |
| 53 | +### Maintenance |
| 54 | + |
| 55 | +- Pinned the `hatchling` build backend to 1.32.4 and capped built |
| 56 | + distributions at core metadata 2.4 so the locked Twine can validate them. |
| 57 | +- Raised the dev and test extras floors to `hatch>=1.18.1` and |
| 58 | + `pytest>=9.0.3`. |
| 59 | + |
3 | 60 | ## 3.6.0 |
4 | 61 |
|
5 | 62 | ### Changed: every API-sourced enum now tolerates unknown values |
|
0 commit comments