a month ago
I've had a railway.json set up with "watchPatterns" for several months and over the past few weeks have been noticing deployments being skipped that previously would have been deployed.
My config:
"watchPatterns": ["/services/backend/**", "/packages/**", "/package.json"]Has there been a change in behavior in how "watchPatterns" is matching paths?
I'm noticing that deployments with changes in the "backend" directory are non-deterministically being skipped.
3 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
I see the same right now: https://github.com/hypercerts-org/ePDS/pull/76
I wonder if it's related to https://railway.com/changelog/2026-04-03-skip-rebuilds ? Although I don't have that feature flag enabled...
Status changed to Open Railway • about 1 month ago
25 days ago
Just saw this again: https://github.com/hypercerts-org/ePDS/pull/113
The PR changes files in packages/shared, and watchPatterns includes packages/shared/**, yet I see:
21 days ago
Doubling down on this, I have multiple project ( apps/web, apps/api, apps/admin...) deployed from a monorepo , only api have packages/records-pdf on his watch patterns, and on a commit that modify packages/records-pdf, api is the only on who is note redeploy. Every other repo are being deployed whereas packages/records-pdf is not on their watch patterns.
Is there still no answer from railway team ?
Attachments