Skip to content

ci(release): use --legacy-peer-deps for npm ci#149

Merged
rubenvdlinde merged 1 commit into
betafrom
fix/release-legacy-peer-deps
May 9, 2026
Merged

ci(release): use --legacy-peer-deps for npm ci#149
rubenvdlinde merged 1 commit into
betafrom
fix/release-legacy-peer-deps

Conversation

@rubenvdlinde
Copy link
Copy Markdown
Contributor

Summary

Release workflow fails at npm ci because eslint-plugin-jsdoc ^62.9.0 (root) and ^46.2.6 (peer of @nextcloud/eslint-config@8.4.2) conflict, and npm ci is strict by default. Using --legacy-peer-deps brings the workflow in line with how local dev handles the same conflict.

Without this fix, beta-channel publishes are blocked. Run #25600382893 (PR #144 release) failed at this step.

Changes

  • .github/workflows/release.yml — both npm ci invocations gain --legacy-peer-deps

The current root devDependencies pin eslint-plugin-jsdoc ^62.9.0 but
@nextcloud/eslint-config@8.4.2 declares a peer of ^46.2.6. npm ci is
strict and refuses the resolution; npm install --legacy-peer-deps is
how the rest of the codebase handles this conflict locally. Bringing
the workflow in line so the release run can complete.
@rubenvdlinde rubenvdlinde merged commit bb5790a into beta May 9, 2026
0 of 2 checks passed
@rubenvdlinde rubenvdlinde deleted the fix/release-legacy-peer-deps branch May 9, 2026 11:50
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 9, 2026

🎉 This PR is included in version 1.0.0-beta.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

rubenvdlinde added a commit that referenced this pull request May 9, 2026
PR #149 added `--legacy-peer-deps` to release.yml's npm ci to skip
the npm 11 peer-dep ERESOLVE failure on @vue/eslint-config-typescript.
Code Quality (which gates PR merges) was missed and still uses bare
`npm ci`, so any new PR fails Frontend Quality with the same conflict
the release flow already works around.

Bring code-quality.yml in line.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant