From da3584f6abdd8be0e97f9c3b827793d3d7d22a49 Mon Sep 17 00:00:00 2001
From: David Colburn <xero73@gmail.com>
Date: Thu, 3 Sep 2026 16:18:54 -0400
Subject: [PATCH 1/2] Cut 1.1.0

Bump the version constant and populate the changelog for the three
user-visible changes that have accumulated since 1.0.0: the unified
start_egress method, the PASSTHROUGH encoding preset, and the now-required
exp claim on token verification.
---
 CHANGELOG.md           | 16 ++++++++++++++++
 lib/livekit/version.rb |  2 +-
 2 files changed, 17 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index c978915..cd17c1e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,21 @@
 ## [Unreleased]
 
+## [1.1.0]
+
+### Added
+
+- `EgressServiceClient#start_egress`, a unified egress entry point taking a single source (`template:`, `web:`, or `media:`), a list of `outputs:`, an optional default `storage:` for outputs that don't set their own, and per-request `webhooks:`. Reachable as `egress.start_egress` from `LiveKit::LiveKitAPI`.
+- `EncodingOptionsPreset::PASSTHROUGH`, selectable through the existing `preset:` kwarg on `start_egress`, which skips transcoding for a single-track egress.
+
+### Changed
+
+- **Breaking:** `LiveKit::TokenVerifier#verify` now requires an `exp` claim and raises `JWT::MissingRequiredClaim` for a token without one. Tokens minted by `LiveKit::AccessToken` always set `exp`, so this only affects tokens issued elsewhere with no expiry.
+- The `jwt` runtime dependency now requires `>= 2.3.0` (was `>= 2.2.3`), for `required_claims` support.
+
+### Removed
+
+- `UpdateEgressRequest` from the generated protobuf stubs, following the removal of the unused `UpdateEgress` RPC upstream. It was never reachable through any client method.
+
 ## [1.0.0]
 
 ### Added
diff --git a/lib/livekit/version.rb b/lib/livekit/version.rb
index 99f3d49..29aac94 100644
--- a/lib/livekit/version.rb
+++ b/lib/livekit/version.rb
@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module LiveKit
-  VERSION = "1.0.0"
+  VERSION = "1.1.0"
 end

From f8768195abb8ed0f055d42f6723edb5cdee80fe8 Mon Sep 17 00:00:00 2001
From: David Colburn <xero73@gmail.com>
Date: Thu, 3 Sep 2026 22:50:38 -0400
Subject: [PATCH 2/2] Sync Gemfile.lock to 1.1.0

The gemspec is a path gem, so its version is pinned in Gemfile.lock. Bumping VERSION without updating the lockfile fails test-api.yml, which installs with bundler-cache (frozen mode) and rejects a stale lockfile.
---
 Gemfile.lock | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Gemfile.lock b/Gemfile.lock
index 56cd698..6387193 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    livekit-server-sdk (1.0.0)
+    livekit-server-sdk (1.1.0)
       faraday (>= 2.0, < 3.0)
       google-protobuf (~> 4.30, >= 4.30.2)
       jwt (>= 2.3.0, < 3.0)