fix(deps): restore installable @babel/core and stylelint-config-html constraints - #554
Merged
Merged
Conversation
…constraints PRs #506 (@babel/core 8.0.1) and #504 (stylelint-config-html 2.0.0) were merged into development, but neither major is installable against the app's current upstream pins. `npm ci` on development now fails with ERESOLVE, which breaks every frontend job. - @nextcloud/webpack-vue-config@7.0.4 (latest) declares peer @babel/core "^7.22.9" — no published 7.x accepts Babel 8. - stylelint-config-html@2.0.0 requires peer postcss-html "^2.0.0", but @nextcloud/stylelint-config@3.2.2 (latest) pins stylelint-config-recommended-vue "^1.6.1", which pins postcss-html "^1.0.0". Reverts both constraints to the last installable values. Verified with npm ci, stylelint, eslint, webpack production build and vitest.
Contributor
Quality Report — ConductionNL/buildiq @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| check-manifest | ✅ | ||||
| test-l10n | ✅ | ||||
| check-gitignore | ✅ | ||||
| check-nc-floor | ✅ | ||||
| format | ✅ | ||||
| check-l10n-js | ✅ | ||||
| check-schema-l10n | ✅ | ||||
| composer | ✅ | ✅ 106/106 | |||
| npm | ✅ | ✅ 640/640 | |||
| app:check-code | ⏭️ | ||||
| info.xml | ✅ | ||||
| REUSE | ❌ | ||||
| PHPUnit | ✅ | ||||
| Newman | ✅ | ||||
| Playwright | 🚨 NO VERDICT — enabled but never ran | ||||
| Hydra gates | ✅ |
Quality workflow — 2026-08-30 09:15 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
PRs #506 (
@babel/core7.29.7 -> 8.0.1) and #504 (stylelint-config-html1.1.0 -> 2.0.0) were merged intodevelopmentwhile their CI was red. Neither major is installable against this app's current upstream pins, sonpm ciondevelopmentnow fails withERESOLVEand every frontend job is broken.Reproduced on
development@ 46db69e with npm 11 (the versionenginesrequires):The two upstream ceilings
@babel/core8 —@nextcloud/webpack-vue-config@7.0.4is the latest published version and declarespeer @babel/core "^7.22.9". Every published 7.x (7.0.0 - 7.0.4) carries the same range. No release accepts Babel 8.stylelint-config-html2 — it requirespeer postcss-html "^2.0.0", but@nextcloud/stylelint-config@3.2.2(latest) pinsstylelint-config-recommended-vue "^1.6.1", which pinspostcss-html "^1.0.0". Bumping the whole cluster tostylelint-config-recommended-vue@2.0.0does not help — it just relocates the conflict onto@nextcloud/stylelint-configitself.Both unblock only when Nextcloud publishes updated configs.
What this does
Restores the two constraints to their last installable values (
@babel/core: ^7.26.9,stylelint-config-html: ^1.1.0) and regeneratespackage-lock.json. No source changes.Verified locally (npm 11)
npm cinpm run stylelintnpm run lint(eslint)npm run build(webpack production)npm test(vitest)Follow-up
stylelint-config-htmlandpostcss-htmlare redundant direct devDependencies —stylelint.config.jsextends only@nextcloud/stylelint-config, and both packages arrive transitively viastylelint-config-recommended-vue. Dropping both direct pins was verified to keepnpm ciclean with byte-identical stylelint output, and would stop this conflict recurring.