Skip to content

Force npm self-install in release workflow #258

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mishushakov merged 1 commit into from
Apr 23, 2026
+1 −1
Merged

Force npm self-install in release workflow #258

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -342,13 +342,13 @@
run: |
pnpm config set auto-install-peers true
pnpm config set exclude-links-from-lockfile true

- name: Update npm
run: |
npm install -g npm@^11.6
npm install -g --force npm@^11.6
npm --version

- name: Install dependencies

Check notice on line 351 in .github/workflows/release.yml

View check run for this annotation

Claude / Claude Code Review

Deprecated ::set-output syntax in charts-release job 

The charts-release job's 'Output new version' step uses the deprecated '::set-output' workflow command (disabled by GitHub in May 2023), so 'needs.charts-release.outputs.version' is always empty on modern runners. This is a pre-existing issue unrelated to this PR's change, but since this PR already touches release.yml it's a good time to fix line 176 to use 'echo "version=$(...)" >> $GITHUB_OUTPUT'.
Comment thread
mishushakov marked this conversation as resolved.
run: pnpm install --frozen-lockfile

- name: Create new versions
Expand Down
Loading