Suggested upgrade to development version of node in Dockerfile

[daveisfera]

Is there an existing issue for this?

• I have searched the existing issues

Package ecosystem

Docker

Package manager version

No response

Language version

No response

Manifest location and content before the Dependabot update

FROM node:24.14.1-trixie-slim

WORKDIR /usr/src/app

dependabot.yml content

version: 2
updates:
    - package-ecosystem: "github-actions"
      directory: "/"
      schedule:
          interval: "weekly"
    - package-ecosystem: "docker"
      directory: "/"
      schedule:
          interval: "weekly"

Updated dependency

FROM node:25.9.0-trixie-slim

What you expected to see, versus what you actually saw

No recommended update

Native package manager behavior

N/A

Images of the diff or a link to the PR, issue, or logs

Bump node from 24.14.1-trixie-slim to 25.9.0-trixie-slim

Smallest manifest that reproduces the issue

FROM node:24.14.1-trixie-slim

[caugner]

Node 25.9.0 is the current stable version, not the development version. Node 24.14.1 is the current LTS version.

You should be able to @dependabot ignore this major version if you want to skip Node 25.

[robaiken]

Hi @daveisfera , Dependabot doesn't have a concept of Node LTS vs current when parsing Docker tags, it just sees 25.9.0 as a newer version than 24.14.1 and suggests the bump. Node 25 is the current release line and not LTS, but that distinction isn't something the Docker updater can infer from the tag alone.

If you want to stay on the 24.x LTS line, you can ignore majors in your config:

- package-ecosystem: "docker"
  directory: "/"
  schedule:
    interval: "weekly"
  ignore:
    - dependency-name: "node"
      update-types: ["version-update:semver-major"]