Skip to content

fix: Accept primary address update as JSON body instead of query param #3

fix: Accept primary address update as JSON body instead of query param

fix: Accept primary address update as JSON body instead of query param #3

Triggered via push February 11, 2026 21:08
Status Success
Total duration 1m 3s
Artifacts 1

ci.yml

on: push
Matrix: Test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Test (3.14)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0+O+MaQAAAABghTKe8+SdSY3ybBT2O5CoUEhMMzBFREdFMDExMQBFZGdl
Test (3.14)
Failed to restore: Cache service responded with 400
Build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0GPCMaQAAAACmu3loxL3pRYZJbGodADmkRE0yRURHRTA3MTYARWRnZQ==
Build
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
dist-40ec7615e3fb99d166abbd8437912d3e1ea5cf7d Expired
167 KB
sha256:25e56dc54fb839c21e98c0b17253c4d4cf09baae7980e50edaf4039d753ac6ba