Skip to content

Next.js security vulnerabilities in pnpm-lock.yaml block deployment on Railway #55

@computerpoet

Description

@computerpoet

Problem

Deploying RefRef on Railway fails because Railway's deployment security scanner detects vulnerable Next.js versions in pnpm-lock.yaml:

Railway requires next@>=15.1.11 and next@>=16.0.10.

Root cause

  1. apps/webapp/package.json and apps/www/package.json specify next@16.0.7 — needs bump to >=16.0.10
  2. pnpm-lock.yaml still resolves next@15.1.2 (likely a stale transitive dependency) — needs lockfile regeneration after the bump

Suggested fix

pnpm -F @refref/webapp add next@^16.0.10
pnpm -F @refref/www add next@^16.0.10
pnpm install  # regenerate lockfile, should drop stale 15.1.2

Environment

  • Railway deployment (Docker-based, security scanner enabled by default)
  • RefRef commit: 8895d31741b04aa77387697e095928dbc75e652b

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions