Skip to content

security: pin the Node base image by digest so its patches reach the live siteΒ #423

Description

@devantler

πŸ€– Generated by the Agentic Engineer (interactive Claude Code session)

Problem

Both stages of the image use node:26-alpine, a floating tag with no digest. Dependabot can only propose a new tag (it did once, 22-alpine β†’ 26-alpine in #54), never a rebuilt image behind the same tag. So the operating-system and Node patch updates the server runs on reach guests only when a release rebuilds the image, and #408's release rule for base-image updates never fires for them.

Evidence

  • The only Dependabot Docker update in the history is build(deps): bump node from 22-alpine to 26-alpineΒ #54 (2026-05-24), a tag change. The Docker ecosystem is configured weekly in .github/dependabot.yml, and no patch-level update has ever been proposed.
  • The runtime stage is the server guests reach, so its patch level matters more than the build stage's.

Hypothesis

If both stages pin node:26-alpine by digest, Dependabot proposes each rebuilt image as a reviewed build(deps) update, and #408 releases it, so the server's base stays within one weekly cycle of upstream and two builds of the same commit produce the same image.

Success signal and window

  • Within two weekly cycles after merge, Dependabot opens a digest update, and once merged it cuts a patch release.

Smallest useful change

Acceptance criteria

  • Both stages are pinned by digest, and the toolchain check accepts the pinned form.
  • After merge, a Dependabot digest update is opened, merged and released.

Rough size

S.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Fields

    No fields configured for Security.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions