Skip to content

Update pnpm migration note and workflow snippets - #2243

Merged
bluwy merged 1 commit into
mainfrom
update-some-docs
Aug 12, 2026
Merged

Update pnpm migration note and workflow snippets#2243
bluwy merged 1 commit into
mainfrom
update-some-docs

Conversation

@bluwy

@bluwy bluwy commented Aug 12, 2026

Copy link
Copy Markdown
Member

No description provided.

@changeset-bot

changeset-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 13f1771

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

@netlify

netlify Bot commented Aug 12, 2026

Copy link
Copy Markdown

Deploy Preview for changesets ready!

Name Link
🔨 Latest commit 13f1771
🔍 Latest deploy log https://app.netlify.com/projects/changesets/deploys/6a7bd491ca498500087dd987
😎 Deploy Preview https://deploy-preview-2243--changesets.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment thread site/guide/migration.md
This only affects pnpm projects. When Changesets checks whether a package is unpublished, it now follows pnpm's registry behavior and ignores scope-based `publishConfig` registry overrides and `publishConfig.registry`.

If you relied on either field for this check, make sure v3 selects the registry you expect from your pnpm and npm configuration.
If you relied on either field for this check, migrate the config to an [`.npmrc` file](https://docs.npmjs.com/cli/configuring-npm/npmrc) instead.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

The previous note was kinda vague, this gives a bit of direction.

@codecov

codecov Bot commented Aug 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.53%. Comparing base (fdfdc93) to head (13f1771).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2243   +/-   ##
=======================================
  Coverage   84.53%   84.53%           
=======================================
  Files          80       80           
  Lines        3168     3168           
  Branches      890      890           
=======================================
  Hits         2678     2678           
  Misses        433      433           
  Partials       57       57           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bluwy
bluwy added this pull request to the merge queue Aug 12, 2026
Merged via the queue into main with commit 0434573 Aug 12, 2026
18 checks passed
@bluwy
bluwy deleted the update-some-docs branch August 12, 2026 08:53
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