-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
Description
Is there an existing issue for this?
- I have searched the existing issues
Package ecosystem
npm
Package manager version
pnpm 9.15.9 and pnpm 10.7.1
dependabot support pnpm catalog according to release.
Language version
Node.js v22.12.0
Manifest location and content before the Dependabot update
packages:
- packages/*
catalog:
lodash: 4.0.0dependabot.yml content
version: 2
updates:
# Enable version updates for npm
- package-ecosystem: "npm"
# Look for `package.json` and `lock` files in the `root` directory
directory: "/"
# Check the npm registry for updates every day (weekdays)
schedule:
interval: "daily"Updated dependency
- lodash: 4.0.0 -> 4.17.21
PR: azu/pnpm-catalog-with-dependabot#1
What you expected to see, versus what you actually saw
Expected
dependabot should update pnpm-workspace.yaml and pnpm-lock.yaml.
- Update pnpm-workspace.yaml's catalog to 4.17.0
- Update pnpm-lock.yaml to 4.17.0
Actual
dependabot only update pnpm-lock.yaml.
- pnpm-workspace.yaml's catalog is not updated
- pnpm-lock.yaml is updated to 4.17.0
It causes another issue:
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
- pnpm 10 Bump lodash from 4.0.0 to 4.17.21 azu/pnpm-catalog-with-dependabot#1
- pnpm 9 Bump lodash from 4.0.0 to 4.17.21 azu/pnpm9-catalog-with-dependabot#1
both has same issue. the behavior is same.
Smallest manifest that reproduces the issue
Context
It seems that the dependabot update pnpm catalogs is not working as expected. The last successful run was on 2025-03-28T17:54:36+09:00 in my private repo, and since then, it has not been able to update the pnpm catalogs.
Ilia-TheNetworkFirm, osuzu-4, aoman-n, osadi, martinmachma and 25 more
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done