railway environment edit accepts --project
Introduced 2026-05-10 · score 0.96
HOW TO USE IT
When editing service configuration in a project that is not linked locally, pass the project and environment explicitly. Use `--service-config` with the service, dot path, and value; add `--stage` to stage changes without committing.
railway environment edit --project <project-id> --environment <environment-id> --service-config <service> <dot.path> <value>railway environment edit --project <project-id> --environment <environment-id> --service-config <service> <dot.path> <value> --stageWHY THIS HELPS
Stage or apply service configuration changes for a project that is not linked to the local directory.
BEFORE THIS CHANGE
Without `--project`, the command required a locally linked project; the linked project remained the default.
REQUIREMENTS AND LIMITATIONS
- Version: v4.57.2
- --project, -p <PROJECT_ID>: Select the project; the release note says it resolves from this option when provided, otherwise from the linked project.
- --environment, -e <ENV>: Select the environment to edit. Required with `--project` when no linked context exists, per the release note.
- --service-config, -s <SERVICE> <PATH> <VALUE>: Configure a service using a dot path; provide the service, property path, and value.
- --stage: Stage changes without committing.
- When using `--project` without linked context, `--environment` is required.
FIRST-PARTY EVIDENCE
- https://github.com/railwayapp/cli/releases/tag/v4.57.2
- https://github.com/railwayapp/cli/pull/892
- https://docs.railway.com/cli/environment
Check the installed version and the source before using it. Entry JSON