Open romainmenke opened 1 year ago
Just a friendly reminder that this issue is still present.
We currently work around it but it takes away a bit of the magic of dependabot grouped updates :)
This is still an issue :)
Hi @romainmenke ; does this still occur? The crew has shipped quite a few improvements in recent weeks.
This was still an issue very recently : https://github.com/stylelint/stylelint/pull/7560
Hi it looks like all of the dependencies were correctly grouped and updated in https://github.com/stylelint/stylelint/pull/7560/files
And the info looks correct in the PR body too.
Is the issue still present? @romainmenke
It is still present :)
I fix it manually : https://github.com/stylelint/stylelint/pull/7560/commits/298cc9ed479c24db3ca0a47dcc399f89576ed165
The PR comment body has indeed improved! I missed that.
So it is partially resolved?
Ah thanks I missed that. Will take a look!
I pulled the peer dependency relationship between these packages
I also made a minimal repro of the issue with just the 3 dependencies
"dependencies": {
"@csstools/css-parser-algorithms": "^2.3.0",
"@csstools/css-tokenizer": "^2.1.1",
"@csstools/media-query-list-parser": "^2.1.2"
}
I'll step through our Dependabot CLI and see if there's a way to improve peer dependency updates!
I found that the #updated_requirements method doesn't run for the peer dependency updates. I'm not sure how the peer dependency is getting updated in the first place though, because @csstools/css-parser-algorithms
updates with requirements_to_unlock: :own
Hi all, just checking in on where we stand with this issue. Thanks in advance!
Is there an existing issue for this?
Package ecosystem
npm
Package manager version
latest
Language version
latest
Manifest location and content before the Dependabot update
package.json
before : https://github.com/stylelint/stylelint/blob/2c45589a4b730b2c7c0d2ffd75815ad3c9ac963f/package.json#L134-L136package-lock.json
before : https://github.com/stylelint/stylelint/blob/2c45589a4b730b2c7c0d2ffd75815ad3c9ac963f/package-lock.json#L1221-L1232package.json
after : https://github.com/stylelint/stylelint/blob/8ca025e55178d16c1786ce99c4d596c2ad99cb64/package.json#L134-L136package-lock.json
after : https://github.com/stylelint/stylelint/blob/8ca025e55178d16c1786ce99c4d596c2ad99cb64/package-lock.json#L1221-L1238dependabot.yml content
https://github.com/stylelint/stylelint/blob/2c45589a4b730b2c7c0d2ffd75815ad3c9ac963f/.github/dependabot.yml#L1-L32
Updated dependency
What you expected to see, versus what you actually saw
I expected two things to be different :
package.json
Neither was true.
@csstools/css-tokenizer
was only updated inpackage-lock.json
and this change wasn't mentioned in the PR commentIn this specific case the real change was in
@csstools/css-tokenizer
as this package had a minor version bump with new features.It was this change that should have been carefully reviewed as it is a direct dependency.
I suspect this is what happened :
@csstools/css-parser-algorithms
comes before@csstools/css-tokenizer
@csstools/css-parser-algorithms
the lock file already contained@csstools/css-tokenizer
version2.2.0
(it is a peer dependency)@csstools/css-tokenizer
is already up to date in the lock file, it was skippedA possible fix would be to first build a dependency graph and then execute updates in topological order instead.
Then
@csstools/css-tokenizer
would have been updated first.Native package manager behavior
N/A
Images of the diff or a link to the PR, issue, or logs
https://github.com/stylelint/stylelint/pull/7109/commits/8ca025e55178d16c1786ce99c4d596c2ad99cb64
Smallest manifest that reproduces the issue
No response