- add the mit LICENSE and set license and author in all package.json
files, plus a license section in the readme
- generate the license notices of all shipped production dependencies
and node.js in a dockerfile stage and serve them at /licenses.txt,
linked from the sidebar footer
- keep license files when slimming node_modules in the image
- add oci labels, with the version passed in by ci
- document licensing in the development docs
- bump version to 1.22.2
- use REGISTRY (git.hq.ars9.space) for login and image tags instead of
deriving it from the server url, which is the runner's registration
address and may be internal-only
- document how jobs reach gitea when the runner uses an internal address
- run server lint, type-check, tests and build, and client lint, build
and storybook tests on master and pull requests
- when a push to master changes the package.json version, build the
docker image and push it to the gitea registry tagged with the
version and latest
- document the workflow and the REGISTRY_TOKEN secret
- install production dependencies and chromium in a separate stage
- drop source maps, typescript sources and declarations, docs,
typeorm's browser build, better-sqlite3's c sources and ffmpeg
- base the runtime on debian:bookworm-slim with only the node binary
- document the image layout
- bump version to 1.22.1
- list the snippets a scenario uses in the export dialog, checked by
default, with the versions the scenario uses
- export each selected snippet once per used version (latest and
pinned) via the new snippetIds query parameter
- resolve used snippets from the exported version's steps
- show the scenario version in the export dialog
- document the export query parameters
- bump version to 1.22.0
- replace synchronize with migrations, starting with a generated initial
migration that adopts databases created by synchronize
- apply pending migrations in the docker container before the server,
and refuse to start the server while migrations are pending
- share one entity list and data source between app, migration runner,
typeorm cli and tests; tests run the real migrations
- add migration:run, migration:show and migration:generate scripts and
a test that fails when entities and migrations differ
- exit with code 1 when startup fails
- bump version to 1.20.0
- allow the vite dev server origins in development and the compose port
origins in production; CORS_ORIGINS overrides both
- set NODE_ENV=production in the runtime docker image
- document both settings in .env.example and the development docs
- bump version to 1.19.3
- load .env in compose only when it exists; every setting has a default
- comment out every setting in .env.example, with ## for descriptions
and # VAR=default for settings to uncomment
- update README, development docs and CLAUDE.md accordingly
- rewrite architecture, development, mcp and scenario docs to match the
current code: single container, all mcp tools, runs, versioning,
timeouts, settings, client routing and dev setup
- rewrite README as a general overview without liquio-specific wording
- remove the unused KEYS_DIR setting and ./keys compose mount
- remove the unused result parameter from step code execution
- complete .env.example with the file storage settings and fix the
DB_PATH default
- base the docker image on node:24-slim and require node >=24 via
engines in the root package.json
- read app name and version from the workspace root package.json for
config, swagger, startup log and mcp server info; drop the server
workspace version
- bind test http servers to 127.0.0.1 so tests pass in containers
without ipv6 loopback
- bump version to 1.19.1
- serve the built client from the server via serve-static (CLIENT_DIR),
falling back to index.html outside /api, /mcp, /docs and /health
- replace server and client Dockerfiles and nginx with one root
Dockerfile and a single liqa compose service on port 13000
- use Playwright's chromium-headless-shell with only its required libs
and DejaVu/Liberation fonts instead of Debian chromium and Noto
- clear the npm cache in the runtime image
- bump version to 1.19.0
- add POST /import, an import page and the import_yaml mcp tool; items
are validated up front and imported in dependency order
- switch list page import buttons to the central import
- write scenario exports as separate --- yaml documents per entity
- give each test app its own files dir to avoid cross-suite races
- use node: prefix for node built-in imports
- bump version to 1.18.0
- add DELETE /scenarios/:id/runs/:runId/files/:fileId and the
delete_run_file MCP tool; the stored file is removed once no scenario
or run references it
- add a delete button with confirmation to the run detail files table
- bump version to 1.17.0
- snapshot scenario and snippet content into version tables on every
content change; live tables keep holding the latest version
- record the scenario version on each run and copy its steps into the
run steps, so runs execute and show the version they were created with
- keep run step history when a step is deleted (FK set null)
- pin a snippet version with runSnippet('alias@N')
- add version picker to the run modal and version info across the UI
- add version list/get endpoints and MCP tools
- include version in exports and require it on import, restoring the
exact version by id + version
- record a trace for each scenario run and upload it as trace.zip
- add PLAYWRIGHT_TRACE_MODE (on, retain-on-failure, off) as the default
- add a trace mode option to the run modal, stored per run and reused
by repeat run; expose the default via GET /scenarios/run-defaults
- accept traceMode in POST /scenarios/:id/run and run_scenario MCP tool
- share one run modal component between scenario list and detail pages
- git-ignore server/data
- Add context.assert(fn, description) for function assertions
- Logs outcome on success/failure, throws on assertion failure
- Bump package version from 1.8.0 to 1.9.0
Scenario steps can now persist in-script generated content (e.g. an
obtained VC's JWT) as a run file via context.downloadFile('data:...'),
without needing a network fetch. Bumps to 1.8.0.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- POST /exec now accepts environmentId (UUID) and credentials (alias → UUID)
instead of raw payloads; resolves entities via EnvironmentService and
CredentialService before passing data to browserService.exec
- exec_code MCP tool updated with same schema: environmentId + credentials map
- CredentialModule imported into BrowserModule and McpModule
- docs(scenario): rewrite script runtime section for single context argument
- docs(mcp): update exec_code description to reflect new parameter shapes
- style: reorder imports across server source (formatter)
- replace (page, context, helpers) signature with async (context) => {}
- add ScriptContext interface exposing page, browser, env, getEnv,
getCredential, getStepOutput, runSnippet, dumpDom, log/warn/error
- rename getEnvUrl to getEnv throughout service and docs
- fix step ordering: normalizeStepOrder and run step rows are now 1-based
- migrate existing DB rows (scenario_steps, scenario_run_steps) +1
- update all tests and stored snippet/step code in DB to new API
- add client workspace section to architecture diagram and description
- split development.md commands into server and client per-workspace
- document client tech stack, directory layout, routing, and theming
- add Client overview section with Storybook test instructions
- add output column to ScenarioRunStepEntity; exec step return value is JSON-serialised and stored
- expose helpers.getStepOutput(order) in exec code; negative order is relative to current step
- add get_scenario_run, wait_for_scenario_run, export_scenario, import_scenario MCP tools
- move Architecture, Key descriptors, MCP tools, Scenario, Development docs to docs/
- delete CONTRIBUTING.md (replaced by docs/development.md)