chore: bump version to 2.4.9

2.4.8 already shipped with the full-scan retry fix; this release adds
the opt-in --upload-logs streaming channel.

Author: barslev

CHANGELOG.md

@@ -1,13 +1,15 @@
 # Changelog
 
-## 2.4.8
+## 2.4.9
 
 ### Added: opt-in streaming log channel via `--upload-logs`
 
 - New `--upload-logs` flag (default off). When set, each CLI invocation registers a run, reports a per-run status (`in_progress` / `success` / `failure` / `cancelled`), and uploads a transcript of its own log output to the Socket backend for that run, visible in the Socket admin views. The transcript is captured regardless of the local `--enable-debug` state; the existing terminal verbosity is unchanged.
 - New `--no-upload-logs` flag (mutually exclusive with `--upload-logs`) explicitly opts the run out of uploading logs, even when an org-level override would otherwise enable it. Use this when you need a guaranteed no-upload guarantee (e.g. legal/consent reasons).
 - The Socket backend can also force-enable streaming for specific orgs in the absence of an explicit opt-out. The feature is best-effort — registration or upload failures silently degrade and never block the scan.
 
+## 2.4.8
+
 ### Fixed: retry transient full-scan upload failures
 
 - The full-scan upload (`POST /orgs/<org>/full-scans`) now retries transient

pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "socketsecurity"
-version = "2.4.8"
+version = "2.4.9"
 requires-python = ">= 3.11"
 license = {"file" = "LICENSE"}
 dependencies = [