Skip to content

feat: Migrate to pnpm 10#181

Merged
joshsny merged 2 commits intomainfrom
pnpm-10
Nov 26, 2025
Merged

feat: Migrate to pnpm 10#181
joshsny merged 2 commits intomainfrom
pnpm-10

Conversation

@rafaeelaudibert
Copy link
Copy Markdown
Member

No description provided.

Copy link
Copy Markdown
Member

@edwinyjlim edwinyjlim left a comment

Choose a reason for hiding this comment

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

looks pretty straightforward and it ran fine on my machine

but what about the .github/workflows/publish? I see unpinned pnpm versions here

      - name: Install pnpm
        run: npm install -g pnpm

      - name: Install package.json dependencies with pnpm
        run: pnpm install

      - name: Build the package
        run: pnpm build
        
      - name: Publish the package in the npm registry
        run: pnpm publish --access public

@rafaeelaudibert
Copy link
Copy Markdown
Member Author

@edwinyjlim That github action looks at the packageManager key on package.json when deciding what version to use and figures out it should use 10.23.0.

@joshsny joshsny merged commit e5b2112 into main Nov 26, 2025
14 checks passed
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