chore(deps): move to @conduction/nextcloud-vue 2.2.0-vue3.1 - #730
Merged
Conversation
The 3.0.0-vue3.* line is being withdrawn from npm. The major was cut from a real BREAKING CHANGE footer (the retired action-list flow editors), but it applied to a prerelease channel only our own apps consume, so the line is resumed at 2.x rather than carried forward. 2.2.0-vue3.1 is a superset of 3.0.0-vue3.6 — it additionally carries the recovered Vue 2 -> Vue 3 component conversion and the CnGraphCanvas port/loop work. Despite the lower version number this is not a downgrade in content. The lockfile is regenerated with npm 10.8.2, matching CI's node 20 toolchain. Local npm 11 prunes optional entries that do not apply to the current platform, which makes CI's `npm ci` fail with "Missing: ... from lock file"; running `npm ci` locally does not reproduce it because npm 11 accepts its own lockfile. Verified: `npx npm@10.8.2 ci --dry-run` exits 0, and `USE_LOCAL_LIB=false npm run build` exits 0 with no unresolved modules. The USE_LOCAL_LIB=false is load-bearing — this repo's webpack aliases @conduction/nextcloud-vue to a sibling ../nextcloud-vue/src checkout when one exists, so a plain build can silently compile the sibling's source instead of the package under test.
Contributor
Quality Report — ConductionNL/procest @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| check-manifest | ✅ | ||||
| check-vue3-compile | ✅ | ||||
| test-l10n | ✅ | ||||
| composer | ✅ | ✅ 100/100 | |||
| npm | ✅ | ✅ 550/550 | |||
| PHPUnit | ✅ | ||||
| Newman | ⏭️ | ||||
| Playwright | ✅ |
Quality workflow — 2026-08-05 12:03 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.
Moves off the withdrawn
3.0.0-vue3.*line onto the resumed 2.x prerelease line.The 3.0 major was cut from a genuine
BREAKING CHANGE:footer (the retired action-list flow editors), but it applied to a prerelease channel only our own apps consume, so the line is resumed at 2.x rather than carried forward. The six3.0.0-vue3.*versions are being withdrawn from npm once every app is off them.Despite the lower version number this is not a downgrade in content.
2.2.0-vue3.1is a superset of3.0.0-vue3.6: it additionally carries the recovered Vue 2 -> Vue 3 component conversion (196 specs, 137 components, 51 missingemits) and the CnGraphCanvas port/loop work.Verification
Two traps had to be stepped around, so the evidence is stated precisely:
npm cifail withMissing: pinia@4.0.2 / vite@8.2.0 ... from lock file. Runningnpm cilocally does not reproduce it — npm 11 accepts the lockfile it just wrote. Verified withnpx npm@10.8.2 ci --dry-run(exit 0).USE_LOCAL_LIB=false npm run build(exit 0, no unresolved modules). That flag is load-bearing: this repo'swebpack.config.jsaliases@conduction/nextcloud-vueto a sibling../nextcloud-vue/srccheckout whenever one exists, so a plain build can silently compile the sibling's source instead of the package under test.