Skip to content

chore(deps): repin @conduction/nextcloud-vue to 2.2.0-vue3.3 (3.0.0-vue3.6 was unpublished) - #433

Merged
rubenvdlinde merged 1 commit into
developmentfrom
fix/ncvue-repin-2.2.0-vue3.3
Aug 5, 2026
Merged

chore(deps): repin @conduction/nextcloud-vue to 2.2.0-vue3.3 (3.0.0-vue3.6 was unpublished)#433
rubenvdlinde merged 1 commit into
developmentfrom
fix/ncvue-repin-2.2.0-vue3.3

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Why

@conduction/nextcloud-vue 3.0.0-vue3.13.0.0-vue3.6 were unpublished from npm, and npm never permits reuse of an unpublished version number — so the old pin is permanently dead:

$ npm view @conduction/nextcloud-vue@3.0.0-vue3.6 version
npm error code E404 — No match found for version 3.0.0-vue3.6

npm ci therefore cannot succeed on development. Fleet-blocking.

What

Old pin 3.0.0-vue3.6dead (E404)
New pin 2.2.0-vue3.3 — live, current vue3 dist-tag
Dead refs in package-lock.json 3 → 0

Pinned exactly (no caret), per fleet convention.

Verification

  • Lockfile regenerated with npm 10.8.2, not local npm 11. CI runs node 20 / npm 10; an npm-11-written lockfile prunes platform-inapplicable optional entries, making CI's npm ci fail Missing: … from lock file while a local npm ci still passes. Using npm 10 avoids that false green.
  • Cold npm ci (fresh isolated cache, npm 10.8.2): exit 0, zero Missing: lines.
  • Build USE_LOCAL_LIB=false npm run build: exit 0, 0 Module not found, 0 export … was not found. (USE_LOCAL_LIB=false matters — webpack.config.js aliases the package to a sibling ../nextcloud-vue/src checkout when present, so a plain build can compile the sibling and prove nothing about the pin.)
  • Unit tests — both suites in this repo:
    • npm run test:unit (vitest): 18 files / 210 tests passing
    • npm test (jest): 9 suites / 120 tests passing
      A "before" run is impossiblenpm ci cannot install the dead pin, so no baseline number exists to compare against.
  • UI-surface check: all 27 identifiers src/ imports from @conduction/nextcloud-vue resolve against the installed 2.2.0-vue3.3 (574 exports, counting the export * from '@nextcloud/vue' re-export in nc-vue's ESM entry). Run with a sentinel positive control to confirm the checker can actually report a miss. The 2.x line is a renumbering of the same lineage, so the surface is a superset — nothing lost.

Scope

Only package.json + package-lock.json. The bundle is gitignored here (no tracked js//dist/). E2E (playwright) not run — needs a live Nextcloud instance.

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/softwarecatalog @ 99cff84

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
check-vue-demi
test-l10n
composer ✅ 121/121
npm ✅ 849/849
PHPUnit
Newman ⏭️
Playwright
Hydra gates

Quality workflow — 2026-08-05 15:28 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit cd5259a into development Aug 5, 2026
28 of 30 checks passed
@rubenvdlinde
rubenvdlinde deleted the fix/ncvue-repin-2.2.0-vue3.3 branch August 5, 2026 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant