Skip to content

fix(simulations): commit scenario ids to scenarios.yaml - #112

Merged
u9g merged 1 commit into
mainfrom
jason/scenario-ids
Oct 16, 2026
Merged

u9g merged 1 commit into
mainfrom
jason/scenario-ids

Conversation

@u9g

@u9g u9g commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Problem

Since lk v2.19.0, a scenarios file needs an id on the group and on every scenario, so LiveKit can track a scenario across runs as its text changes. This starter's scenarios.yaml has none, so:

  • .github/workflows/simulations.yml fails on its first run: scenarios.yaml is missing 4 scenario id(s); re-run with --yes to have them added to the file.
  • Running lk agent simulate text --scenarios scenarios.yaml locally stops at an "Add scenario IDs?" prompt that rewrites the file you just cloned.

Fix

Commit the ids. They were generated by the CLI itself (lk agent simulate text --scenarios scenarios.yaml -y). Nothing else in the file changes.

Verification

With lk built from livekit-cli main, against a staging project, all 3 scenarios ran and passed.

lk v2.19.0 requires an `id` on the scenario group and on every scenario.
Without them, the simulations workflow fails in CI with "scenarios.yaml is
missing 4 scenario id(s); re-run with --yes to have them added to the file",
and a local run stops to ask whether to rewrite the file.

The ids were generated by `lk agent simulate text --scenarios scenarios.yaml -y`.
@u9g
u9g merged commit e965b2c into main Oct 16, 2026
5 checks passed
@u9g
u9g deleted the jason/scenario-ids branch October 16, 2026 00:11
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.

2 participants