release: promote dev to production (MCP-14, Railway integration + config as code) - #48
Merged
Merged
Conversation
Gateway and Web are now connected to this repo in Railway (dev -> Development, main -> Production, Wait for CI on), so drop the GitHub Actions deploy jobs, the railway-deploy scripts and their test, and the docs for the never-configured RAILWAY_*_TOKEN deploy secrets. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GET/PATCH /projects/:id/skill-runtime encoded the Fluent SkillAssignment and SkillRuntimeEvent models directly, so the dashboard received camelCase property names (plus internal fields such as client identity, request hash and detail JSON). Recent events rendered blank, and saved assignments could not be resubmitted. Map both to explicit snake_case response DTOs with only browser-needed fields, and rename the section to Recent Runtime Events. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tion ci: deploy through the Railway GitHub integration
Railway stops reading railway.json-style config files on 2026-12-01. Define Gateway and Web source/build/deploy settings (plus the Postgres database, its volume, and preserve() entries for every service variable, since apply deletes anything undeclared) in .railway/railway.ts, with the branch chosen per environment. Remove railway/gateway.json and railway/web.json and their CI check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The runtime-settings PATCH round trip passed locally only because a local env file set FRONTEND_URL; CI has none, so the origin check returned 403. Set FRONTEND_URL in the test app and send that origin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s-code # Conflicts: # docs/test-plans/README.md
chore: move Railway service config to Config as Code
fix: return snake_case runtime assignments and events (MCP-14)
App sleeping was switched on for Gateway and Web in both environments after the Config as Code cutover. A sleeping Gateway pauses its retention, billing and analytics schedulers and gives MCP clients a cold start, so declare sleepApplication: false for both services. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix: keep Railway services awake
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes
dev(ecb36d6) tomain. Development was validated before promotion.Included
railway-deploy*scripts are removed..railway/railway.tsandrailway/*.jsonis removed (Railway stops reading those on 2026-12-01).sleepApplication: falsefor Gateway and Web.Production impact
/). Merging lets the integration buildmainafter CI passes, which ships the MCP-14 Gateway and Web changes.🤖 Generated with Claude Code