Skip to content

Remove npm check and upgrade step#216

Merged
2-one-week merged 1 commit into
mainfrom
2-one-week-patch-1
Apr 14, 2026
Merged

Remove npm check and upgrade step#216
2-one-week merged 1 commit into
mainfrom
2-one-week-patch-1

Conversation

@2-one-week

Copy link
Copy Markdown
Member

Removed npm upgrade step from workflow.

Related Issue

Describe your changes

Request

Removed npm upgrade step from workflow.
@2-one-week 2-one-week requested a review from a team as a code owner April 14, 2026 05:11
@npayfebot

Copy link
Copy Markdown
Collaborator

🔍 No files have been changed

Latest commit: 976467d

Please check your commit.

If packages_dir is not specified or only markdown files are in the changes, detection may fail.

powered by: naverpay changeset detect-add actions

@ttppggnnss ttppggnnss left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

감사합니다 🙇‍♂️

@2-one-week 2-one-week merged commit 7c3f8ac into main Apr 14, 2026
8 checks passed
@2-one-week 2-one-week deleted the 2-one-week-patch-1 branch April 14, 2026 05:13
@npayfebot

Copy link
Copy Markdown
Collaborator

🔍 No files have been changed

Latest commit: 976467d

Please check your commit.

powered by: naverpay size-action

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — removing the redundant npm upgrade step is a clean simplification since the project uses pnpm.

Extended reasoning...

Overview

This PR removes a single CI step (Check and upgrade npm) from .github/workflows/publish.yaml. The removed step printed the current npm version, ran npm install -g npm@latest, then printed the upgraded version. No other files are touched.

Security Risks

None. Removing a npm install -g npm@latest step has no security implications — if anything, it reduces the surface area by not pulling an unpinned external package at runtime.

Level of Scrutiny

Minimal. This is a one-file, 8-line deletion in a CI workflow with no logic change. The project uses pnpm throughout (setup via pnpm/action-setup@v4, installs via pnpm install --frozen-lockfile), so upgrading npm was unnecessary noise.

Other Factors

No bugs were reported, no outstanding reviewer comments exist, and the change is fully mechanical. Safe to approve without human review.

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.

3 participants