Skip to content

ci: build broken — node:16 base too old for current npm + passport-url 404 (unrelated to Verdaccio) #1580

Description

@evereq

ever-demand CI build is broken (independent of the Verdaccio work)

The docker-build-publish.yml build fails for the client images due to a base image too old for the current npm, and the API image hits an npm registry 404. These are pre-existing and unrelated to the internal-Verdaccio wiring (PR #1579) — the inserted VERDACCIO_REGISTRY block runs fine and is a no-op when the var is unset.

1. node:16-alpine base too old (5 of 6 images: admin-web-angular, carrier/merchant/shop-mobile-ionic, shop-web-angular)

The base-image setup step fails:

#14 npm ERR! notsup Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0"}
       Actual:   {"npm":"8.11.0","node":"v16.15.1"}

npm i -g npm pulls a version of npm that no longer supports Node 16. Fix: bump the base image in the .deploy/*/Dockerfile files (and any node:16* refs) to a supported Node LTS (e.g. node:22-alpine), and re-verify the native build deps (snappy, vips, node-gyp) still compile.

2. API image — passport-url@1.0.4 404

During yarn bootstrap, passport-url@1.0.4 returns 404 from the registry. If that version is unpublished on npm it will fail on the public registry too — audit/replace the dependency (or pin a published version).

Notes

  • Builds now run on our in-cluster ARC runners (RUNNER_LINUX_X64 org var was just set for the org).
  • The DigitalOcean push steps should also be gated behind vars.DO_ENABLED (separate cleanup, in progress).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions