Skip to content

chore(deps): move to @conduction/nextcloud-vue 2.2.0-vue3.1 - #730

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

chore(deps): move to @conduction/nextcloud-vue 2.2.0-vue3.1#730
rubenvdlinde merged 1 commit into
developmentfrom
chore/ncvue-2.2.0-vue3.1

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

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 six 3.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.1 is a superset of 3.0.0-vue3.6: it additionally carries the recovered Vue 2 -> Vue 3 component conversion (196 specs, 137 components, 51 missing emits) and the CnGraphCanvas port/loop work.

Verification

Two traps had to be stepped around, so the evidence is stated precisely:

  • Lockfile 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: pinia@4.0.2 / vite@8.2.0 ... from lock file. Running npm ci locally does not reproduce it — npm 11 accepts the lockfile it just wrote. Verified with npx npm@10.8.2 ci --dry-run (exit 0).
  • Build run as USE_LOCAL_LIB=false npm run build (exit 0, no unresolved modules). That flag is load-bearing: this repo's webpack.config.js aliases @conduction/nextcloud-vue to a sibling ../nextcloud-vue/src checkout whenever one exists, so a plain build can silently compile the sibling's source instead of the package under test.

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.
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ 840292d

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.

@rubenvdlinde
rubenvdlinde merged commit d33aa12 into development Aug 5, 2026
33 of 35 checks passed
@rubenvdlinde
rubenvdlinde deleted the chore/ncvue-2.2.0-vue3.1 branch August 5, 2026 12:04
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