develop #6

Merged
SebastienDenooz merged 7 commits from develop into main 2026-09-27 23:38:35 +00:00
No description provided.
The runner's job image (node:24-bookworm) has no Docker client, so the
build, scan and push steps could not run. The job now installs Docker's
own client and Buildx from its Debian repository, and works on the
docker-in-docker engine the runner gives its jobs through DOCKER_HOST.
chore(release): 1.0.0
All checks were successful
CI / docker (pull_request) Successful in 1m14s
CI / quality (pull_request) Successful in 1m44s
CI / e2e (chromium) (pull_request) Successful in 3m19s
CI / e2e (firefox) (pull_request) Successful in 4m59s
CI / e2e (webkit) (pull_request) Successful in 5m55s
40a51711cc
test(e2e): keep parallel tests apart from instance-wide changes and sign-in load
All checks were successful
CI / docker (pull_request) Successful in 1m1s
CI / quality (pull_request) Successful in 1m41s
CI / e2e (chromium) (pull_request) Successful in 2m35s
CI / e2e (firefox) (pull_request) Successful in 3m45s
CI / e2e (webkit) (pull_request) Successful in 4m51s
2c34f1951d
With 12 workers on one test server, tests saw each other's changes:

- Seeded environments get the documented defaults explicitly, not the
  instance's current ones, which the settings test changes meanwhile;
  that test keeps 127.0.0.1 in its allowlist for the webhook tests.
- The pinned-message limit is lowered under the settings lock.
- The sign-in throttle test uses an account and a client address of its
  own (the test server trusts 127.0.0.1 as a proxy), so its failures no
  longer count against the address every test signs in from.
- In CI, Playwright runs 4 workers per job (PW_WORKERS overrides it),
  and loginAs waits 15 s for the redirect of a sign-in on a busy server.
A save the server stored but whose answer was lost (an error after the
change, a dropped connection) reverted the editor to its previous list:
the next change was then made on that list and silently removed the
stored tags. After a failed save, the editor now re-reads the tags the
server stores; a change made while a save fails is still sent, and the
error clears once a later save succeeds.
fix(home): keep a navigation started before the redirect to the last environment
Some checks failed
CI / quality (pull_request) Successful in 1m38s
CI / docker (pull_request) Successful in 55s
CI / e2e (chromium) (pull_request) Failing after 2m9s
CI / e2e (firefox) (pull_request) Successful in 3m5s
CI / e2e (webkit) (pull_request) Successful in 4m11s
1089bb24fb
The home page redirects to the last (or first) environment once mounted.
On a slow machine, the user could click an environment before that, and
the redirect then replaced their choice. The redirect is now skipped
when a navigation away from the home page has already started.
fix(tags): show a change in the stored order so that the answer moves no chip
All checks were successful
CI / quality (pull_request) Successful in 1m38s
CI / docker (pull_request) Successful in 56s
CI / e2e (chromium) (pull_request) Successful in 2m11s
CI / e2e (firefox) (pull_request) Successful in 3m12s
CI / e2e (webkit) (pull_request) Successful in 4m17s
36c47a319b
The tag input keys its chips by position and appends a new tag, while the
server stores tags sorted: when the answer arrived, the chips moved, and
a click on a chip at that moment removed another tag. The editor now
shows each change as the server stores it (trimmed, duplicates removed
case-insensitively, in SQLite's NOCASE order), so the answer changes
nothing on screen.
test(e2e): wait for the navigation before reloading, and for the palette to filter before clicking
All checks were successful
CI / quality (pull_request) Successful in 1m35s
CI / e2e (chromium) (pull_request) Successful in 2m9s
CI / docker (pull_request) Successful in 56s
CI / e2e (firefox) (pull_request) Successful in 3m7s
CI / e2e (webkit) (pull_request) Successful in 4m18s
633459942c
The environment header shows the clicked environment as soon as its
route middleware loaded it, before the URL changes: the audit test could
reload the previous environment. The command palette filters its list
just after the input changes: the palette test could click an item that
was moving. Both tests now wait for the state they rely on.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Alchemic.Studio/Trapbox!6
No description provided.