Open
Conversation
75e64a5 to
80ff3a7
Compare
80ff3a7 to
5644b18
Compare
5644b18 to
bef27a0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.0.4→11.0.2Release Notes
sindresorhus/np (np)
v11.0.2Compare Source
f0859d9v11.0.1Compare Source
e6a8dafv11.0.0Compare Source
Breaking
307ebecImprovements
1ef9af73ded31e--no-release-notesflag4f910a2--remoteflag to specify Git remote4d5fb6a7dcd8333ed286a6b51dda5a96f80efcc05ed8f3322ebb9acfFixes
--contentsflag not being respected when publishing53904d0c6ef15d02b4ed9packageManagerfield is missing7009b770a8af7bebdcbaaa651fc43811182e996c6f3804d0bpublishConfighandling for access and registry fields753abb4a13bba267b6aff869f80b08a3f64a160aff6a11153contentsconfig option being ignored88226d7contentsoption being interpreted as package name521ecfcfea3eb7getNpmPackageAccessto respectpublishConfig.registry15040c8publishConfig.registryis official npm registry380fd24v10.3.0Compare Source
npm loginon authentication failure38abeee0ad9a8c005ebdbv10.2.0Compare Source
bun.locklock file (#761)8187dfea45f816v10.1.0Compare Source
cbc6f3b8fdac0cv10.0.7Compare Source
publishConfig.registryto be npm default registry when using Yarn berry (#750)6c5eee3v10.0.6Compare Source
pnpmand--any-branchor--branch(#745)d0c1493v10.0.5Compare Source
34409bev10.0.4Compare Source
4caa295v10.0.3Compare Source
02f60c7v10.0.2Compare Source
770418fv10.0.1Compare Source
9fdebd5v10.0.0Compare Source
Breaking
--yarnflag (#730)4b3b599--package-manager. See below.Improvements
--package-managerflag (#730)4b3b599packageManagerfield in package.json.npwill default to reading package.json, and look for lockfiles to determine the best package manager as a last resort.4b3b599v9.2.0Compare Source
8d3a984819ed29v9.1.0Compare Source
0d9522bv9.0.0Compare Source
Breaking
6c2e00eImprovements
c31c2bcad7b09eConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.