Skip to content

ci(dependabot): align Dependabot configuration - #1925

Open
caugner wants to merge 1 commit into
mainfrom
sync-dependabot-config
Open

caugner wants to merge 1 commit into
mainfrom
sync-dependabot-config

Conversation

@caugner

@caugner caugner commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Description

Aligns the Dependabot configuration with the MDN defaults:

  • Sets open-pull-requests-limit: 10 on the github-actions entry and the npm entry
  • Sets a 3-day cooldown on the github-actions entry and the npm entry
  • Adds the npm entries for /vendor/yari/client/pwa and /vendor/yari/libs/play

Motivation

Ensures consistent dependency update configuration across all MDN repositories.

Additional details

See also: https://docs.github.com/en/code-security/dependabot/working-with-dependabot/dependabot-options-reference

Related issues and pull requests

Part of #1445.

@caugner
caugner requested review from a team and LeoMcA and removed request for a team September 17, 2026 20:28
@github-actions

Copy link
Copy Markdown
Contributor

a9c3abc was deployed to: https://fred-pr1925.review.mdn.allizom.net/

Comment thread .github/dependabot.yml
Comment on lines +74 to +116
- package-ecosystem: npm
directory: /vendor/yari/client/pwa
schedule:
interval: weekly
open-pull-requests-limit: 10
cooldown:
default-days: 3
groups:
npm-prod:
dependency-type: production
update-types:
- minor
- patch
npm-dev:
dependency-type: development
update-types:
- minor
- patch
commit-message:
prefix: chore
include: scope

- package-ecosystem: npm
directory: /vendor/yari/libs/play
schedule:
interval: weekly
open-pull-requests-limit: 10
cooldown:
default-days: 3
groups:
npm-prod:
dependency-type: production
update-types:
- minor
- patch
npm-dev:
dependency-type: development
update-types:
- minor
- patch
commit-message:
prefix: chore
include: scope

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we intentionally left these out?

@caugner
caugner marked this pull request as ready for review September 18, 2026 14:52
@caugner
caugner requested a review from a team as a code owner September 18, 2026 14:52
Comment thread .github/dependabot.yml
include: scope

- package-ecosystem: npm
directory: /vendor/yari/client/pwa

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two new entries (/vendor/yari/client/pwa here, /vendor/yari/libs/play on line 97) target manifests that fred never installs, so every PR Dependabot opens for them will change versions that have no effect on the build.

Fred consumes the vendored source and resolves its dependencies from the root package.json:

  • rspack.config.js:602 bundles ./vendor/yari/client/pwa/src/service-worker.ts as a fred rspack entry, and server.js:18 imports ./vendor/yari/libs/play/index.js directly.
  • Root package.json declares no workspaces, and .github/workflows/_build.yml:99, .github/workflows/test.yml:32 and :83 only run npm ci at the root — nothing installs vendor/yari/client/pwa/yarn.lock or vendor/yari/libs/play/package-lock.json.
  • The real versions are the root ones: @zip.js/zip.js, dexie, he and @types/he are all declared in root package.json.

The pins have already drifted, which confirms the vendored manifests are dead weight: vendor/yari/client/pwa/package.json pins dexie 4.0.11 and @zip.js/zip.js 2.7.71, while the root declares ^4.4.6 and ^2.15.0. The pwa's webpack, webpack-cli and ts-loader devDependencies are also unused, since rspack does the bundling.

Remove both entries and keep the vendored code covered by the root / npm entry. Note also that neither new entry carries the root entry's typescript >=7 ignore rule, so they would open TypeScript 7 PRs that the root entry is deliberately suppressing.

AI-generated review by Claude

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, that explains it.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants