Commit 0d02999
ci(deploy-watch): print Railway's own error instead of guessing at the token type
The first live run failed on "Could not resolve environmentId from the token",
which is the right guard but a dead end diagnostically — it reports what did not
happen and swallows what Railway actually said. The response body carries the
real message and contains no credential, so there was never a reason to hide it.
Also captures the probe with `|| true`, because `curl -sSf` under `set -e` would
abort the step on a non-2xx before the diagnostic could ever print — the failure
mode most worth seeing was the one guaranteed to stay invisible.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QwrqK15CtSW1sWAyEzopco1 parent a06ae5a commit 0d02999
1 file changed
Lines changed: 12 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
61 | 61 | | |
62 | 62 | | |
63 | 63 | | |
64 | | - | |
65 | | - | |
66 | | - | |
67 | | - | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
68 | 74 | | |
| 75 | + | |
| 76 | + | |
69 | 77 | | |
70 | 78 | | |
71 | 79 | | |
| |||
0 commit comments