- Refactored context menu action tests for collections and requests to use sequential tagging.
- Improved readability and consistency in test structure and assertions.
- Updated drag-and-drop tests for cross-project interactions to enhance clarity and maintainability.
- Ensured proper handling of asynchronous operations and improved test reliability.
A public repository cannot call a reusable workflow in the internal
KSAI repository, so the setup workflow fails before any job starts
with "workflow was not found". Call the published snapshot instead,
pinned to the current release and following its consumer template,
with every command enabled and a review on each opened pull request.
The snapshot names no model gateway of its own, so the call passes the
organization's gateway variable. It runs on GitHub-hosted runners,
because the Kong runner pool serves no public repository, and with no
GitHub App at all: push_as_app is false and no key is passed, so every
read and write goes through GITHUB_TOKEN.
Signed-off-by: Bart Smykla <bartek@smykla.com>
- Restrict GITHUB_TOKEN to contents:read at the workflow level in
insomnia-test.yml and playwright.yml
- Pin peaceiris/actions-gh-pages to a commit hash instead of a mutable tag
- Cap the x-reply-delay-ms test header to 60s in echo-server.js,
event-stream-server.js, and mcp-server.js to avoid unbounded timers
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Two independent papercuts in the circular reference check, both hit while
investigating a failure on another PR.
`npm run check-cycle-references` could not run on Windows at all. It spawned
the extensionless `node_modules/.bin/depcruise` shim through `execFileSync`,
which Windows cannot launch; the `.cmd` sibling does not help either, since
Node >=18 refuses to spawn `.cmd` without a shell (CVE-2024-27980). Resolve
dependency-cruiser's own entry point and run it with `process.execPath`
instead — no shell, works everywhere.
The check also fails on baseline drift (cycles recorded in the baseline that
no longer exist), which is correct: the baseline is a ratchet, and leaving a
fixed cycle in it would silently keep permitting its reintroduction. But CI
labelled every non-success outcome "New circular references detected", so a PR
that *removed* two cycles was reported as having added some. That cost real
debugging time.
Give the script distinct exit codes — 1 for a new cycle, 2 for drift alone —
and have the workflow capture and map them to separate messages. The failure
behaviour is unchanged; only the wording is now accurate. Renamed the final
step to match what it actually gates on.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
- Implement tests for sidebar drag-and-drop persistence across views.
- Add tests for sidebar filtering and pinning functionality.
- Create onboarding tests for sidebar focus mode.
- Verify settings dialogs and inline renaming in the sidebar.
- Ensure correct tree hierarchy rendering for requests and folders.
- Test tab name and method synchronization with underlying requests.
- Validate tab management features including pinning, switching, and closing.
- Enhance URL bar functionality tests, including undo behavior and environment variable previews.
- Introduce TypeScript configuration for improved type safety and module resolution.
## Summary
- Replaces the madge-based `check-cycle-references` with a `dependency-cruiser`-based check, cruised once per npm workspace package.
- Keeps the checker, dependency-cruiser config, and known-cycle baseline together under `scripts/circular-references/`.
- Uses a committed baseline to grandfather existing cycles while failing on new cycles and stale baseline entries.
- Cleans the existing `insomnia-inso` type cycle by using `insomnia-data`'s `AllTypes` instead of importing the database container type.
- CI explicitly uses Bash for correct `tee`/pipeline failure propagation, safely handles skipped checks, and posts a PR report.
- Dropped `madge`/`.madgerc`, added `dependency-cruiser`.
Bob Qiu