Open vinceAmstoutz opened 10 months ago
@weaverryan @kbond Any idea ?
In addition, I also tried to delete all the entries in the dependabot GitHub actions cache, without success.
@greysteil @feelepxyz Any idea?
Sorry @vinceAmstoutz - I haven't worked on Dependabot for years. No insight to share!
Sorry @vinceAmstoutz - I haven't worked on Dependabot for years. No insight to share!
Thanks for you response @greysteil! No idea how to globally ignore a dependency (ignored even from the scan)? Thanks for allin advance!
I think the problem is that the symfony components switched to path based entries at some point, but those paths are only available after running composer install
.
Unfortunately I am not really sure how to work around this. Ignoring those dependencies is not going to work (I think). My knowledge of Ruby and the inner workings of the dependabot ecosystem setup is also too limited to understand if adding a composer install
step optionally in some way, shape or form is viable or not.
Is there an existing issue for this?
Package ecosystem
npm
Package manager version
pnpm 8.14.3
Language version
Node 20.11
Manifest location and content before the Dependabot update
package.json
dependabot.yml content
Updated dependency
"@symfony/ux-react": "file:vendor/symfony/ux-react/assets",
What you expected to see, versus what you actually saw
Ignore
@symfony/ux-react
completely and don't throw an error when dependabot looks for dependency updates. I'm using importmap using symfony/ux (official doc here) for @symfony/ux-react dep onlyNative package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Smallest manifest that reproduces the issue