chore(dependabot): hold back the four majors that cannot be adopted - #854
Merged
Conversation
Dependabot re-proposes these on every run, and each one takes `npm ci` or
`npm run build` from green to red with no code change in this repository that
can fix it. Closing the pull requests does nothing: without an ignore rule they
come straight back.
Each is blocked by a package we do not control, verified against the registry
rather than assumed:
- typescript 7 typescript-eslint hard-throws on TS >= 7 (a `versionMajor
>= 7` guard in its dist/index.js) and every published
version still peers `typescript: ">=4.8.4 <6.1.0"`.
- webpack-cli 7 @nextcloud/webpack-vue-config 7.0.4, the LATEST, peers
`webpack-cli: ^6.0.1`.
- @babel/core 8 the same package peers `@babel/core: ^7.22.9`.
- @babel/preset-env preset-env 8 requires core 8, so the pair moves together
or not at all. Splitting them is what broke filinq.
These are COMPATIBILITY limits, not security ones. `npm audit` reports no
advisory against any version pinned here, so holding them costs no exposure.
Lift each the moment its blocker ships support.
Deliberately NOT held: stylelint 17, vitest 4 and pinia 4. All three were
blocked earlier today and all three are now adoptable, so dependabot should
keep proposing them.
Contributor
Quality Report — ConductionNL/stackiq @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| check-manifest | ✅ | ||||
| check-vue-demi | ✅ | ||||
| test-l10n | ✅ | ||||
| format | ✅ | ||||
| check-schema-l10n | ✅ | ||||
| check-l10n-js | ✅ | ||||
| composer | ✅ | ✅ 130/130 | |||
| npm | ✅ | ✅ 713/713 | |||
| app:check-code | ⏭️ | ||||
| info.xml | ✅ | ||||
| REUSE | ❌ | ||||
| PHPUnit | ✅ | ||||
| Newman | ⏭️ | ||||
| Playwright | 🚨 NO VERDICT — enabled but never ran | ||||
| Hydra gates | ✅ |
Quality workflow — 2026-08-30 21:08 UTC
Download the full PDF report from the workflow artifacts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Dependabot re-proposes these on every run, and each takes
npm ciornpm run buildfrom green to red with no code change in this repository that can fix it. Closing the pull requests does nothing: without an ignore rule they come straight back. That is the loop this ends.Each blocker, checked against the registry rather than assumed
typescript7typescript-eslinthard-throws on TS >= 7 (aversionMajor >= 7guard in itsdist/index.js), and every published version still peerstypescript: ">=4.8.4 <6.1.0"webpack-cli7@nextcloud/webpack-vue-config7.0.4, the latest, peerswebpack-cli: ^6.0.1@babel/core8@babel/core: ^7.22.9@babel/preset-env8Not a security trade
These are compatibility limits.
npm auditreports no advisory against any version pinned here, so holding them costs no exposure. Lift each the moment its blocker ships support.Deliberately not held
stylelint17,vitest4 andpinia4. All three were blocked this morning and all three are now adoptable, so dependabot should keep proposing them.