mediazard/Railway Image Update

Update Docker image source and redeploy services on Railway via GraphQL API

Trust Signals

name	description	required	default
api-token	Railway API token (account, workspace, or project token)	yes	—
token-type	Token type: 'bearer' for account/workspace tokens (default), 'project' for project-scoped tokens	no	bearer
environment-id	Railway environment ID (UUID)	yes	—
image	Full Docker image URI with tag or digest (e.g. ghcr.io/org/app:sha-abc123)	yes	—
services	Multiline label:service_id pairs. Labels are for logging only. All services receive the same image.	yes	—
first-service	Label of the service to redeploy before all others. Remaining services deploy after wait.	no	""
registry-username	Registry username for private image pull authentication	no	""
registry-password	Registry password or token for private image pull authentication	no	""
resolve-to-digest	Resolve the image tag to a content-addressed digest before passing to Railway. Prevents mutable-tag races. Set to 'false' only if you manage digest pinning yourself.	no	true
allow-mutable-tag	When resolve-to-digest is 'false', allow deploying a mutable tag (latest, main, master, develop, stable, or no tag). Defaults to 'false' to fail fast on unsafe refs.	no	false

name	description
deployed-services	Comma-separated list of service labels that were successfully deployed (always written, even on partial failure)
failed-services	Comma-separated list of service labels that were not deployed (empty on full success; populated on partial or full failure)
image-tag	The resolved image reference that was deployed. When resolve-to-digest is true (default), this is a digest-pinned ref.
deployment-ids	Newline-separated label=deployment-id pairs for each service deployed.