Skip to content
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.

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

chore: upgrade pnpm to latest version #35

Merged
merged 2 commits into from
Feb 18, 2025
Merged

chore: upgrade pnpm to latest version #35

merged 2 commits into from
Feb 18, 2025

Conversation

nikgraf
Copy link
Collaborator

@nikgraf nikgraf commented Feb 18, 2025

In the CI the version does not need to be defined due:

Optional when there is a packageManager field in the package.json.

source: https://github.com/pnpm/action-setup?tab=readme-ov-file#version

@nikgraf nikgraf requested a review from baiirun February 18, 2025 13:09
Copy link

changeset-bot bot commented Feb 18, 2025

⚠️ No Changeset found

Latest commit: 1968ed7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@nikgraf nikgraf force-pushed the ng/upgrade-pnpm branch 2 times, most recently from 3317f3a to 62e8e85 Compare February 18, 2025 13:20
@nikgraf nikgraf merged commit b6d2f12 into main Feb 18, 2025
3 checks passed
@baiirun baiirun deleted the ng/upgrade-pnpm branch February 18, 2025 23:41
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.

2 participants