#13 put the version in the scenario and snippet YAML export filenames, and made the client request that exact version so the file content always matches its name. The e2e test export (Export e2e test button, GET /scenarios/:id/export-e2e, MCP export_e2e_test) still has neither of those:
The zip is always named <slug>-e2e-test.zip (server) / <scenario name>-e2e-test.zip (client), so exports of different versions overwrite each other or can't be told apart.
E2eExportService.buildE2eTestPackage always builds from the scenario's current steps. There's no way to export a specific version.
Proposed changes
Server
GET /scenarios/:id/export-e2e takes an optional ?version=N (same ParseIntPipe({ optional: true }) as /export). It defaults to the latest version.
buildE2eTestPackage(id, version?) reads the steps from scenarioService.findVersion(id, version ?? scenario.version) instead of scenario.steps.
Name the zip <slug>-v<N>-e2e-test.zip and the generated package.json<slug>-v<N>-e2e-test. Optionally, put the version in the generated README header too.
404 for a version that doesn't exist, as /export does.
MCP
export_e2e_test takes an optional version input ("Scenario version to export. Defaults to the latest"), like export_scenario.
ScenarioDetailPage passes scenario.version and downloads as ${scenario.name}-v${scenario.version}-e2e-test.zip.
Docs/tests
Update docs/scenario.md / docs/mcp.md for the new parameter.
Add server tests: the default and explicit version select the right steps, the filename includes the version, and an unknown version returns 404.
Note on snippets
Snippets are resolved the same way as in the YAML export: versions pinned with alias@N are bundled at that version, and unpinned runSnippet("alias") calls get the latest snippet version. Scenario versions don't record which snippet version was latest when they were saved, so an older scenario export can pick up newer snippet code. That's existing behavior and out of scope here.
#13 put the version in the scenario and snippet YAML export filenames, and made the client request that exact version so the file content always matches its name. The e2e test export (`Export e2e test` button, `GET /scenarios/:id/export-e2e`, MCP `export_e2e_test`) still has neither of those:
- The zip is always named `<slug>-e2e-test.zip` (server) / `<scenario name>-e2e-test.zip` (client), so exports of different versions overwrite each other or can't be told apart.
- `E2eExportService.buildE2eTestPackage` always builds from the scenario's current steps. There's no way to export a specific version.
## Proposed changes
**Server**
- `GET /scenarios/:id/export-e2e` takes an optional `?version=N` (same `ParseIntPipe({ optional: true })` as `/export`). It defaults to the latest version.
- `buildE2eTestPackage(id, version?)` reads the steps from `scenarioService.findVersion(id, version ?? scenario.version)` instead of `scenario.steps`.
- Name the zip `<slug>-v<N>-e2e-test.zip` and the generated `package.json` `<slug>-v<N>-e2e-test`. Optionally, put the version in the generated README header too.
- 404 for a version that doesn't exist, as `/export` does.
**MCP**
- `export_e2e_test` takes an optional `version` input ("Scenario version to export. Defaults to the latest"), like `export_scenario`.
**Client**
- `scenarios.exportE2eTestUrl(id, version?)` appends `?version=N`.
- `ScenarioDetailPage` passes `scenario.version` and downloads as `${scenario.name}-v${scenario.version}-e2e-test.zip`.
**Docs/tests**
- Update `docs/scenario.md` / `docs/mcp.md` for the new parameter.
- Add server tests: the default and explicit version select the right steps, the filename includes the version, and an unknown version returns 404.
## Note on snippets
Snippets are resolved the same way as in the YAML export: versions pinned with `alias@N` are bundled at that version, and unpinned `runSnippet("alias")` calls get the latest snippet version. Scenario versions don't record which snippet version was latest when they were saved, so an older scenario export can pick up newer snippet code. That's existing behavior and out of scope here.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
#13 put the version in the scenario and snippet YAML export filenames, and made the client request that exact version so the file content always matches its name. The e2e test export (
Export e2e testbutton,GET /scenarios/:id/export-e2e, MCPexport_e2e_test) still has neither of those:<slug>-e2e-test.zip(server) /<scenario name>-e2e-test.zip(client), so exports of different versions overwrite each other or can't be told apart.E2eExportService.buildE2eTestPackagealways builds from the scenario's current steps. There's no way to export a specific version.Proposed changes
Server
GET /scenarios/:id/export-e2etakes an optional?version=N(sameParseIntPipe({ optional: true })as/export). It defaults to the latest version.buildE2eTestPackage(id, version?)reads the steps fromscenarioService.findVersion(id, version ?? scenario.version)instead ofscenario.steps.<slug>-v<N>-e2e-test.zipand the generatedpackage.json<slug>-v<N>-e2e-test. Optionally, put the version in the generated README header too./exportdoes.MCP
export_e2e_testtakes an optionalversioninput ("Scenario version to export. Defaults to the latest"), likeexport_scenario.Client
scenarios.exportE2eTestUrl(id, version?)appends?version=N.ScenarioDetailPagepassesscenario.versionand downloads as${scenario.name}-v${scenario.version}-e2e-test.zip.Docs/tests
docs/scenario.md/docs/mcp.mdfor the new parameter.Note on snippets
Snippets are resolved the same way as in the YAML export: versions pinned with
alias@Nare bundled at that version, and unpinnedrunSnippet("alias")calls get the latest snippet version. Scenario versions don't record which snippet version was latest when they were saved, so an older scenario export can pick up newer snippet code. That's existing behavior and out of scope here.