Release v0.5.0 #418

Merged
vas2000-work merged 3 commits from release/v0.5.0 into main 2026-07-01 19:02:52 +02:00
Owner

Release cut for v0.5.0 (Cargo.toml package.version 0.4.0 -> 0.5.0). On merge, create-release.yml tags v0.5.0 and build-oci-image publishes the :v0.5.0 image. Cut via the Forgejo web editor to keep the commit server-side.

Release cut for v0.5.0 (Cargo.toml package.version 0.4.0 -> 0.5.0). On merge, create-release.yml tags v0.5.0 and build-oci-image publishes the :v0.5.0 image. Cut via the Forgejo web editor to keep the commit server-side.
Release v0.5.0
Some checks failed
Check / fmt + clippy + build + tests (pull_request) Successful in 2m23s
Integration / integration tests (pull_request) Successful in 9m20s
E2E / Playwright against staging (pull_request) Failing after 1m24s
a4eb28da27
Merge branch 'main' into release/v0.5.0
Some checks failed
Check / fmt + clippy + build + tests (pull_request) Successful in 3m10s
E2E / Playwright against staging (pull_request) Failing after 2m40s
Integration / integration tests (pull_request) Successful in 11m8s
4bca79350c
vas2000-work scheduled this pull request to auto merge when all checks succeed 2026-07-01 18:49:57 +02:00
fix(e2e): run setup in firefox so bearer capture stops flaking on chromium
All checks were successful
E2E / Playwright against staging (pull_request) Successful in 37s
Check / fmt + clippy + build + tests (pull_request) Successful in 1m29s
Create release / Gate (release-branch merges only) (pull_request) Successful in 2s
Create release / Create release from merged PR (pull_request) Successful in 4s
Integration / integration tests (pull_request) Successful in 6m0s
46b6a89103
The setup project drove the SPA login in headless chromium, which crashes intermittently in CI ("Target page, context or browser has been closed") - sometimes before the bearer is even captured (run 2994 died at 3.2s in the in-app-nav locator.count, so the token every api spec needs was never written). The bearer is read off the OIDC /oauth2/token response and is browser-agnostic, and firefox runs the identical SPA login reliably (it passes form-validation on the same runner and never hits the crash). Switch the setup project to Desktop Firefox so token capture is deterministic. The chromium crash itself is a runner-resource issue (container /dev/shm / RAM) tracked in DEV-396; move setup back to Desktop Chrome once that lands.

#PMS-592

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
vas2000-work deleted branch release/v0.5.0 2026-07-01 19:02:53 +02:00
Sign in to join this conversation.
No reviewers
No labels
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
psa-systems/mokosh-server!418
No description provided.