- Add account, JWT session, revocation, cookie and bearer handling.
- Protect server surfaces while preserving public health, manifest and disabled mode.
- Add SQLite migration and focused server regression coverage.
- GET /scenarios/:id/export-e2e and the export_e2e_test MCP tool take
an optional version, defaulting to the latest
- build the test project from that version's steps, name and timeout
- put the version in the zip name (<scenario>-vN-e2e-test.zip), the
generated package name and the README heading
- the Export e2e test button exports the version being viewed
- document the e2e export in scenario.md and mcp.md
- reopen the run events stream with backoff when the browser closes it for good (Firefox drops quiet connections after a network change)
- enable notifications when the permission is granted outside the bell, unless turned off explicitly
- follow permission changes made in the browser's site settings
- highlight the bell while notifications are on
- add RunEventsService and emit run.started / run.finished from the scheduler
- stream run events over SSE at GET /api/v1/scenarios/runs/events with a heartbeat
- add useRunNotifications hook and NotificationToggle (opt-in bell in the side panel footer)
- refresh runs lists when a run finishes
- document the events stream and notifications
Closes#12
- request the exact version being exported via ?version=N so file
content always matches the filename
- name downloads <scenario>-v<N>.yaml and snippet-<alias>-v<N>.yaml
- read answers from /dev/tty: under `curl ... | bash` stdin is the
script itself, so `read` consumed the script's own lines; fall back
to defaults when there is no terminal
- check that docker, the compose plugin and the daemon work and that
compose accepts the generated compose.yaml
- start liqa with `docker compose up -d` in the install directory,
printing the manual start command if a check or the start fails
- examples/self-test: importable scenario, snippets, credential and
environment that test the liqa instance they run on
- CI builds the Docker image only for vX.Y.Z release tags
- bump version to 1.24.3
- add examples/ with a ready-to-import self-test: environment, credential,
snippets and a scenario that creates, runs and checks another scenario
through the liqa REST API and UI, then cleans up
- add test/examples.spec.ts: imports every example and parses its code
- link the examples from README, docs/scenario.md and CLAUDE.md
Closes#6
- trigger the image job on vX.Y.Z tag pushes instead of master pushes
- run server and client checks unconditionally on tags before the build
- fail the build when the tag doesn't match the package.json version
- document the release routine: version bump, changelog and tag are
done on master after work branches are merged
- large run log data blocks start collapsed, with per-block and
expand/collapse-all toggles; limits set by RUN_LOG_DATA_COLLAPSE_BYTES
and RUN_LOG_DATA_COLLAPSE_LINES
- copy logs button copies the filtered logs as plain text
- GET /manifest.json serves the app version and public client settings,
cached by the UI in localStorage
- bump version to 1.24.2
- collapse run log data blocks whose pretty-printed JSON exceeds a byte
or line limit, with a per-block toggle and an expand/collapse-all
button next to the Logs heading
- align data blocks and toggles with the context/message column
- add a "Copy logs" button that copies the filtered logs as plain text
with every data block expanded
- add GET /manifest.json with the app name, version and run log data
limits (RUN_LOG_DATA_COLLAPSE_BYTES / RUN_LOG_DATA_COLLAPSE_LINES)
- load the manifest in the client stale-while-revalidate: localStorage
copy first, refetched per page load and on tab focus after a while
- show the server version in the sidebar footer, with a reload hint
when it differs from the client build
Closes#3
- "Step N passed" log entries carry the step's return value as data
- context.assert takes an optional details argument stored as log data
on failure; step and snippet failure entries name only the assertion
- log output shows elapsed time in whole seconds
- run artifact and scenario file names open the file in a new tab
- bump version to 1.24.1
- "Step N passed" log entry carries the step's return value as data
- context.assert accepts an optional details argument; on failure the
assertion:fail entry stores { details, error } as data
- assertion failures throw AssertionFailedError so "Step N failed" and
"Snippet X failed" entries name only the assertion, without repeating
the details; the step run description keeps the full message
- exported e2e runtime accepts and prints assert details
- log output shows elapsed time in whole seconds, matching the stored
timestamp resolution
- run artifact and scenario file names link to the inline file content
in a new tab
- step and snippet editors open a reference of the script runtime and
its context API from a (?) button next to the Code label
- bump version to 1.24.0
- a (?) button next to the Code label on the step and snippet
create/edit pages opens a reference of the script runtime: globals,
every context member with examples, and pitfalls such as awaiting
getStepOutput and assert
- the reference lives in components/modals/code-help.md and is
rendered as markdown
- Modal takes size="lg" for document-like content; the dialog is
capped to the viewport and its body scrolls, focusable when lg so
the keyboard can scroll it
- docs/scenario.md notes that getStepOutput is async and points to
the in-app reference to keep in sync
- scenario run log entries carry a context (step/snippet/assertion/run)
and a data payload split out from the message, plus a new debug level
- run detail page shows the full log list in a terminal-style viewer
instead of a paginated table
- bump version to 1.23.0
- context.log/warn/error and console.* split arguments: strings join
into message, object/array args are kept out of it and stored as
the log entry's new data column (JSON), so message stays a stable
string regardless of an object's shape
- added a debug log level alongside log/warn/error, including
context.debug() and console.debug() (previously folded into log)
- CSV/Markdown run log export include the data column/block
- LogOutput renders data pretty-printed in a separate block below
the message, and dims debug entries with a dedicated grey token
calibrated to the WCAG AA contrast floor
- scenario_run_logs gains a context column (step:N, snippet:alias,
assertion:pass/fail, run), tracked through a call stack in
CodeExecutorService so nested runSnippet calls tag their own and
inner log lines
- automatic step started/passed/failed entries and the Playwright
trace upload notice are tagged accordingly
- run log export (CSV/Markdown) and the logs search match context
as well as message
- add a LogOutput UI component: a terminal-style log viewer with
level color coding, elapsed-time-since-start timestamps and a
context tag, replacing the generic Table on the run detail page
- show the full log list instead of paginating it, capped to a
scrollable block
- fix migrations.spec.ts's revert test, which only undid the last
migration instead of all of them
- server and client jobs only run when their directory (or shared
root files) changed, via a new changes job using dorny/paths-filter
- the version job now checks the registry for an existing image tag
of the current package.json version instead of diffing against the
previous commit's package.json, so the image job is skipped once
that version has already been pushed
- the image job tolerates server/client being skipped rather than
requiring both to succeed
- scripts/install.sh prompts for install directory, port and version,
then writes a compose.yaml using the published registry image and
creates a data/ directory for the SQLite volume
- README documents a one-line curl | bash install using the script's
raw URL on the Gitea instance
- add a step to tag each version-bump commit as v<version>, annotated
with that version's changelog entry verbatim
- push tags with git push --follow-tags
- 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
- raise the jest test timeout to 30s: building the nest app in
beforeAll can exceed the 5s default when all suites start at once
- accept any run status when reading back a just-created run, since
the scheduler may already have picked it up
- 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
- add a RevealableCodeBlock ui component that renders its code only
after the user clicks Reveal, with a storybook story
- use it for the data section of the credential page
- bump version to 1.21.1
- show a circle colored by the first 6 hex digits of the uuid,
bordered with the badge text color for contrast in both themes
- lighten the uuid badge background on hover
- let Badge accept a className
- add a storybook story with six sample uuids and a randomize button
- bump version to 1.21.0
- add --color-primary-text for lime used as text or icon color
- stop dimming the idle refresh label with opacity
- darken the light danger button and lighten the dark danger hover
- define syntax highlighting colors per theme as --hl-* tokens
- darken light muted text slightly
- add a storybook contrast page, fail storybook tests on a11y violations
and show live token values in the colors story
- bump version to 1.20.2