I started seeing a new issue over the last 2 days where it seems that the deployment_status is not being communicated to github when relying on the Railway GH integration. Despite not changing my Railway project at all nor my github actions and their settings, when I open a new PR none of my actions are kicking off after the railway deploy finishes.

The github action logic to kick off my e2e tests looks like:

name: PR E2E Tests with Ephemeral DB

on:
  deployment_status:
  pull_request:
    types: [synchronize]

With the intent being that these actions will only run after the deployment has finished. This exact logic was working for me ~4 days ago, but when I opened a PR last night I noticed they were no longer running after the Railway deployment finished successfully and posting to github as seen in the screenshot.

Just to verify, I pushed an additional commit to the open PR to validate whether the other condition which triggers the action ( pull_request: types: [synchronize]) and the action did kick off properly.

Im not sure where/how to validate whether Railway is in fact sending the deployment_status back to github, but my suspicion is that this is broken