---
next_cursor: eyJzY29yZSI6MCwic2VxIjo5MzUsInNpbmNlIjpudWxsLCJ0b29sIjoicmFpbHdheSIsInYiOjF9
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=railway&score=0&cursor=eyJzY29yZSI6MCwic2VxIjo5MzUsInNpbmNlIjpudWxsLCJ0b29sIjoicmFpbHdheSIsInYiOjF9
items: 10
---
# sincecutoff.com changes: railway

## railway logs adds --latest and railway status adds activeDeployments (railway, 2026-01-07)
Published 2026-10-16
- slug: railway-logs-adds-latest-and-railway-status-adds-activedeployments-51f4642b9f90
- score: 0.91

How to use it:

When debugging a Railway service, run `railway logs --latest` to view logs from its latest deployment, and `railway status --json` to inspect the status payload, including `activeDeployments` (added in v4.17.0).

Examples:

```
railway logs --latest
```

```
railway status --json
```

- why_it_matters: Retrieve the latest logs or inspect active deployments while debugging a Railway service.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.17.0>, <https://docs.railway.com/cli/logs>, <https://docs.railway.com/cli/status>, <https://docs.railway.com/cli>
- gotchas: "Version: v4.17.0"; "--latest: For deployment logs, select the latest deployment, even if it failed or is still building."; "--json: Output status in JSON format."; "activeDeployments: Added to `status` output in v4.17.0; current docs do not describe its structure or sub-keys."; "Prerequisite: Authenticate with `railway login` before using the CLI."; "Prerequisite: `railway status` describes the linked project, environment, and resources."

## railway up accepts --project (railway, 2026-01-07)
Published 2026-10-16
- slug: railway-up-accepts-project-63f1ce5a498a
- score: 0.97

How to use it:

When deploying to a selected Railway project, run `railway up` with `--project <project-id>` and `--environment <environment>`; current docs say the environment flag is required with `--project`.

Examples:

```
railway up --project <project-id> --environment <environment>
```

- why_it_matters: Deploy a repository from a selected Railway project.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.17.0>, <https://docs.railway.com/cli/deploying>, <https://docs.railway.com/cli/up>
- gotchas: "Version: v4.17.0"; "--project <ID> (required): Selects the project to deploy to; the current command reference says the default is the linked project."; "--environment <ENV> (required): Selects the deployment environment; current deploying docs require it when using `--project`."; "Prerequisite: The current docs require `--environment` when `--project` is used."; "Prerequisite: For automated deployments, Railway documents using a Project Token scoped to an environment."; "Docs conflict: The current docs require `--environment` alongside `--project`; the v4.17.0 release note only says the flag was added and does not state this requirement. The current command reference describes current behavior, which may differ from v4.17.0."

## railway logs accepts --since and --until (railway, 2026-01-08)
Published 2026-10-16
- slug: railway-logs-accepts-since-and-until-2521e4a6a0a4
- score: 0.96

How to use it:

When debugging a repository deployment, run `railway logs` with `--since` and `--until` to fetch logs for a specific time range. Without a log type flag, it fetches deploy logs by default.

Examples:

```
railway logs --since <START_TIME> --until <END_TIME>
```

```
railway logs --service <SERVICE> --environment <ENVIRONMENT> --since <START_TIME> --until <END_TIME>
```

- why_it_matters: Retrieve Railway logs for a specific time range while debugging a repository deployment.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.18.0>, <https://docs.railway.com/cli/logs>, <https://docs.railway.com/cli>
- gotchas: "Version: v4.18.0"; "--since <TIME> (required): Show logs since a specific time; disables streaming. Accepts relative times or ISO 8601 timestamps."; "--until <TIME> (required): Show logs until a specific time; disables streaming. Accepts relative times or ISO 8601 timestamps."; "--service <SERVICE>: Select the service; defaults to the linked service."; "--environment <ENV>: Select the environment; defaults to the linked environment."; "Prerequisite: Install the Railway CLI and authenticate with a Railway account using `railway login`."

## Railway CLI volume list JSON output (railway, 2026-01-08)
Published 2026-10-16
- slug: railway-cli-volume-list-json-output-b6313088edd9
- score: 0.95

How to use it:

When a script needs to inspect Railway volumes, run `railway volume list --json` to print the listing as JSON.

Examples:

```
railway volume list --json
```

- why_it_matters: Read volume listings as JSON in a script that inspects Railway volumes.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.18.1>, <https://docs.railway.com/cli/volume>, <https://docs.railway.com/cli>
- gotchas: "Version: v4.18.1"; "--json: Output in JSON format."; "--service <SERVICE>: Select a service ID."; "--environment <ENV>: Select an environment ID."; "--project <PROJECT_ID>: Select a project ID."; "Prerequisite: Authenticate with a Railway account using `railway login`; for CI/CD, set `RAILWAY_TOKEN` or `RAILWAY_API_TOKEN` as appropriate."

## railway delete adds project deletion (railway, 2026-01-08)
Published 2026-10-16
- slug: railway-delete-adds-project-deletion-0444ee3452a9
- score: 0.93

How to use it:

When project removal is required, run `railway delete` to select a project and confirm deletion, or specify the project with `--project`.

Examples:

```
railway delete --project <ID|NAME>
```

```
railway delete --project <ID|NAME> --yes
```

- why_it_matters: Delete a Railway project from a coding workflow when project removal is required.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.19.0>, <https://docs.railway.com/cli/delete>, <https://docs.railway.com/cli>
- gotchas: "Version: v4.19.0"; "--project <ID|NAME>: Project to delete; omit to select interactively."; "--yes: Skip the confirmation dialog."; "--2fa-code <CODE>: Verification code when two-factor authentication is enabled."; "--json: Output in JSON format."; "Prerequisite: Authenticate with a Railway account before using the CLI (`railway login`)."; "Prerequisite: Install the Railway CLI."

## railway run accepts --project (railway, 2026-01-08)
Published 2026-10-16
- slug: railway-run-accepts-project-25efb4bddedc
- score: 0.95

How to use it:

When you need to run a repository command using a Railway project other than the linked project, pass `--project <ID>` to `railway run` and provide the command to execute.

Examples:

```
railway run --project <PROJECT_ID> <COMMAND> [ARGS...]
```

- why_it_matters: Run a repository command against a Railway project other than the one currently selected.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.19.0>, <https://docs.railway.com/cli/run>
- gotchas: "Version: v4.19.0"; "--project <ID>: Project ID to use; defaults to the linked project."; "<COMMAND> [ARGS...] (required): Command and arguments to execute."

## railway variable setting reads values from stdin (railway, 2026-01-08)
Published 2026-10-16
- slug: railway-variable-setting-reads-values-from-stdin-ec6191ab6025
- score: 0.92

How to use it:

When a repository workflow supplies a variable value on stdin, set it with `railway variable --set-from-stdin <KEY>`.

Examples:

```
printf '%s' '<value>' | railway variable --set-from-stdin <KEY>
```

- why_it_matters: Set a Railway variable from a value supplied by a repository workflow on stdin.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.19.0>, <https://docs.railway.com/cli/variable>
- gotchas: "Version: v4.19.0"; "--set-from-stdin <KEY> (required): Legacy flag that reads the variable value from stdin; provide the variable key. The docs say it is deprecated but still supported."; "-s, --service <SERVICE>: Select the service to set the variable for."; "-e, --environment <ENV>: Select the environment to set the variable in."; "Docs conflict: Current Railway CLI docs mark `--set-from-stdin KEY` deprecated but still supported; they recommend `railway variable set KEY --stdin` instead. https://docs.railway.com/cli/variable"

## railway link adds a --json flag for CI (railway, 2026-01-08)
Published 2026-10-16
- slug: railway-link-adds-a-json-flag-for-ci-453609edb98a
- score: 0.94

How to use it:

When a CI job needs to link a Railway project with machine-readable output, run `railway link --project <project-id> --environment <environment-id> --json`. The command links the project to the current directory and emits JSON.

Examples:

```
railway link --project <project-id> --environment <environment-id> --json
```

- why_it_matters: Link a Railway project from a CI job that needs machine-readable output.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.20.0>, <https://docs.railway.com/cli/link>
- gotchas: "Version: v4.20.0"; "--project <ID|NAME> (required): Project to link to; CI example uses a project ID."; "--environment <ID|NAME> (required): Environment to link to; CI example uses an environment ID."; "--json: Output in JSON format."

## railway open adds a --print flag (railway, 2026-01-08)
Published 2026-10-16
- slug: railway-open-adds-a-print-flag-3e2d105214b1
- score: 0.94

How to use it:

When a repository workflow needs the linked project’s dashboard URL printed, run `railway open --print` to output it without opening a browser. [Railway `open` docs](https://docs.railway.com/cli/open)

Examples:

```
railway open --print
```

- why_it_matters: Use the Railway CLI's open command in a repository workflow that needs its output printed.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.20.0>, <https://docs.railway.com/cli/open>
- gotchas: "Version: v4.20.0"; "--print (-p) (required): For printing the URL, include this optional flag; it prints the URL instead of opening it."; "Prerequisite: Run from a directory linked to the Railway project whose dashboard URL you need."

## railway CLI adds standalone railway restart command (railway, 2026-01-08)
Published 2026-10-16
- slug: railway-cli-adds-standalone-railway-restart-command-c80dbbbcfb2d
- score: 0.94

How to use it:

When you need to restart a Railway service, run `railway restart`; it restarts the most recent deployment without rebuilding it.

Examples:

```
railway restart
```

```
railway restart --service <SERVICE>
```

```
railway restart --yes
```

- why_it_matters: Restart the Railway resource or service you are working on from the CLI.
- sources: <https://github.com/railwayapp/cli/releases/tag/v4.22.0>, <https://docs.railway.com/cli/restart>, <https://docs.railway.com/cli>
- gotchas: "Version: v4.22.0"; "--service <SERVICE> (-s): Selects the service to restart; defaults to the linked service."; "--yes (-y): Skips the confirmation dialog."; "--json: Outputs in JSON format."; "Prerequisite: Install the Railway CLI and authenticate with `railway login` before using it."; "Prerequisite: The default target is the linked service; use `railway link` to link the project if needed."

Next: https://sincecutoff.com/v1/changes.md?tool=railway&score=0&cursor=eyJzY29yZSI6MCwic2VxIjo5MzUsInNpbmNlIjpudWxsLCJ0b29sIjoicmFpbHdheSIsInYiOjF9
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->