Skip to content

chore(deploy): empty commit to retrigger Railway website build#77

Merged
vivek7405 merged 1 commit into
mainfrom
chore/retrigger-railway-deploy
May 22, 2026
Merged

chore(deploy): empty commit to retrigger Railway website build#77
vivek7405 merged 1 commit into
mainfrom
chore/retrigger-railway-deploy

Conversation

@vivek7405
Copy link
Copy Markdown
Collaborator

Why

PRs #73-#76 each pushed to main but Railway marked every deploy SKIPPED (verified via railway deployment list). The website service's dashboard-set Watch Paths don't include changelog/**, packages/create-webjs/**, packages/webjsdev/**, or .hooks/pre-commit. The live /changelog page is still rendering from PR #72's deploy (19:59).

An empty commit on its own won't change the watch-path math, but it triggers Railway's webhook again and gives the build queue another chance to pick up the latest main, which now includes the regenerated 0.8.5 entry + correct dates.

If this empty-commit push is ALSO SKIPPED, the longer-term fix is to set the website service's Watch Paths to **/* (so changelog changes trigger website rebuilds), per the original intent in #53. Documenting here so the next maintainer knows.

Test plan

@vivek7405 vivek7405 merged commit 2caf24c into main May 22, 2026
@vivek7405 vivek7405 deleted the chore/retrigger-railway-deploy branch May 22, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant