fix(renovate): track the Playwright image tag through npm #340

Merged
ullrich merged 1 commit from renovate-playwright-image-tracks-npm into main 2026-11-15 23:12:52 +00:00
Owner

Summary

Renovate could not update the Playwright container image, so Playwright PRs arrived with only the lockfile changed and failed both browser jobs. #320 is the example: lockfile on 1.65.0, image still on v1.64.1-noble.

Cause. The image was in the playwright group as a docker dependency. MCR publishes no release dates, so the global minimumReleaseAge: "3 days" kept every image update pending and filtered it out of the branch. From a debug lookup:

Marking 2 release(s) as pending, as they do not have a releaseTimestamp and
we're running with minimumReleaseAgeBehaviour=timestamp-required

Fix.

  • A custom regex manager reads mcr.microsoft.com/playwright:v<version>-noble in .forgejo/workflows/*.yml as the npm package playwright. The image tag now gets the same release dates, the same age gate and the same selected version as the lockfile entry, in the same renovate/playwright branch.
  • The docker-datasource view of that image is disabled, so the line is not handled twice.
  • One outdated comment in ci.yml is corrected.

Verification

Local run on this branch: renovate --platform=local --dry-run=lookup with the github-actions and custom.regex managers.

  • All three image tags: 1.64.1 → 1.65.0, updateType: minor, branchName: renovate/playwright, pendingVersions: ["1.65.1"]. This is the same version the Dependency Dashboard shows for the npm packages.
  • The docker dep reports skipReason: disabled.

Not verified:

  • The lookup does not write files, so the actual tag rewrite is unconfirmed until the first real Renovate run. Expected result: Renovate adds the three image tags to #320.
  • pnpm typecheck, lint, test and test:e2e were not run locally; the change touches only renovate.json5 and a workflow comment.

Risk and rollback

  • Config only. Revert this commit to roll back.
  • pnpm dedupe can still move the lockfile to a newer Playwright than Renovate selected (the #38 case). The guard step in the browser jobs still catches that.
  • If the image suffix changes from -noble, the regex stops matching and the tag stops moving. The guard step then fails on the next Playwright bump.

🤖 Generated with Claude Code

## Summary Renovate could not update the Playwright container image, so Playwright PRs arrived with only the lockfile changed and failed both browser jobs. #320 is the example: lockfile on 1.65.0, image still on `v1.64.1-noble`. **Cause.** The image was in the `playwright` group as a docker dependency. MCR publishes no release dates, so the global `minimumReleaseAge: "3 days"` kept every image update pending and filtered it out of the branch. From a debug lookup: ``` Marking 2 release(s) as pending, as they do not have a releaseTimestamp and we're running with minimumReleaseAgeBehaviour=timestamp-required ``` **Fix.** - A custom regex manager reads `mcr.microsoft.com/playwright:v<version>-noble` in `.forgejo/workflows/*.yml` as the npm package `playwright`. The image tag now gets the same release dates, the same age gate and the same selected version as the lockfile entry, in the same `renovate/playwright` branch. - The docker-datasource view of that image is disabled, so the line is not handled twice. - One outdated comment in `ci.yml` is corrected. ## Verification Local run on this branch: `renovate --platform=local --dry-run=lookup` with the `github-actions` and `custom.regex` managers. - All three image tags: `1.64.1` → `1.65.0`, `updateType: minor`, `branchName: renovate/playwright`, `pendingVersions: ["1.65.1"]`. This is the same version the Dependency Dashboard shows for the npm packages. - The docker dep reports `skipReason: disabled`. Not verified: - The lookup does not write files, so the actual tag rewrite is unconfirmed until the first real Renovate run. Expected result: Renovate adds the three image tags to #320. - `pnpm typecheck`, `lint`, `test` and `test:e2e` were not run locally; the change touches only `renovate.json5` and a workflow comment. ## Risk and rollback - Config only. Revert this commit to roll back. - `pnpm dedupe` can still move the lockfile to a newer Playwright than Renovate selected (the #38 case). The guard step in the browser jobs still catches that. - If the image suffix changes from `-noble`, the regex stops matching and the tag stops moving. The guard step then fails on the next Playwright bump. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(renovate): track the Playwright image tag through npm
Some checks failed
CI / Dockerfile Package Check (pull_request) Successful in 4s
CI / Security Scan (pull_request) Successful in 6s
CI / Visual Tests (pull_request) Successful in 35s
CI / Checks (pull_request) Successful in 55s
CI / Journal Image Smoke Test (pull_request) Successful in 56s
CI / E2E Tests (pull_request) Has been cancelled
Cancel superseded CI / Cancel in-flight CI (pull_request) Successful in 3s
05adb392af
The image was in the "playwright" group as a docker dependency, but MCR
publishes no release dates, so the global minimumReleaseAge kept every
image update pending and filtered it out of the branch. #320 arrived
with the lockfile on 1.65.0 and the image still on v1.64.1-noble.

A custom regex manager now reads the workflow image tag as the npm
package `playwright`, so it gets the same release dates, the same age
gate and the same selected version as the lockfile entry. The
docker-datasource view of the same line is disabled.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
ullrich deleted branch renovate-playwright-image-tracks-npm 2026-11-15 23:12:52 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
trails-cool/trails!340
No description provided.