Repository navigation
chore(deps): Stop Dependabot security updates for test packages - #26443
Conversation
Co-Authored-By: Francesco Gringl-Novy <2411343+mydea@users.noreply.github.com>
size-limit report 📦Compared: d97854c (PR test merge using develop at d383066) Against: d383066 (develop) · base run #66362 ✅ Baseline matches: this diff contains only this PR's changes.
|
Optional E2E testsSome optional checks were not successful. They do not block the merge. 2 not successful, 61 successful. See the run.
Successful checks
|
nicohrubec
left a comment
There was a problem hiding this comment.
should we also expand this to integration tests?
|
Good call, done in 2f979cd. The entry now also covers every integration test package that |
What
Dependabot stops opening security update PRs for the E2E test applications and the integration test packages in
dev-packages/.Why
exclude-pathson the root npm entry only applies to version updates. Security updates only use adependabot.ymlentry whosedirectory/directoriesmatch the manifest's own location, so these test packages fell back to the default and got a PR for every advisory (e.g. #26437, #26422). They often pin older versions on purpose, so these PRs are noise.The new entry covers the same test packages that
exclude-pathsalready skips for version updates. It setsopen-pull-requests-limit: 0(version updates only) andignore: '*', which security updates do respect. GitHub's docs confirm thatignoreblocks security updates for named dependencies but don't call out the*wildcard explicitly, so it's worth checking that no new Dependabot PRs for these paths show up after this merges.via @mydea.
--
View Session [Sentry]