Skip to content

Add version input to pin livekit-server release or commit#2

Closed
alan-george-lk wants to merge 1 commit into
livekit:mainfrom
alan-george-lk:feat/version-input
Closed

Add version input to pin livekit-server release or commit#2
alan-george-lk wants to merge 1 commit into
livekit:mainfrom
alan-george-lk:feat/version-input

Conversation

@alan-george-lk

Copy link
Copy Markdown
Contributor

Summary

  • Adds optional version input: release tag (e.g. v1.13.2) or livekit/livekit commit SHA
  • Linux/Windows download release artifacts when a tag is given; macOS and commit pins build from source via go build
  • Preserves existing default behavior (latest release on Linux/Windows, Homebrew on macOS)
  • Adds CI job exercising a pinned commit with data-track schema server config

Motivation

Client SDK e2e tests for data track schema metadata need server commit a47e21b (#4622), which is not yet in a tagged release.

Test plan

  • test-version-pin job builds a47e21b and starts the server with blob config
  • Default test matrix still passes on ubuntu/windows/macos

Made with Cursor

SDK e2e jobs can pass a release tag or livekit/livekit commit SHA so tests
run against server features not yet in the latest release (e.g. data track
schema metadata). macOS and commit pins build from source; Linux and Windows
download release artifacts when a tag is given.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant