chore(deps): update pnpm to v8 #3317
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
4 Participants
Due Date
Depends on
#3331 feat: prepare for pnpm 8
vikunja/frontend
Reference: vikunja/frontend#3317
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/pnpm-8.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
7.32.0
->8.2.0
Release Notes
pnpm/pnpm
v8.2.0
Compare Source
Minor Changes
.npmrc
. This is a convention used by Yarn too.Using
${NAME-fallback}
will returnfallback
ifNAME
isn't set.${NAME:-fallback}
will returnfallback
ifNAME
isn't set, or is an empty string #6018.Patch Changes
-g
to mismatch registries error info when original command has-g
option #6224.pnpm config get <key>
should print boolean values #6360link:
protocol inpackage.json
#6372Our Gold Sponsors
Our Silver Sponsors
v8.1.1
Compare Source
Patch Changes
@yarnpkg/shell
to fix issues in the shell emulator #6320.@
character #6332.preResolution
hook.Our Gold Sponsors
Our Silver Sponsors
v8.1.0
Compare Source
Minor Changes
dedupe-direct-deps
, which is disabled by default. When set totrue
, dependencies that are already symlinked to the rootnode_modules
directory of the workspace will not be symlinked to subprojectnode_modules
directories. This feature was enabled by default in v8.0.0 but caused issues, so it's best to disable it by default #6299.ignore-workspace-cycles
to silence workspace cycle warning #6308.Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v8.0.0
Compare Source
We are excited to announce the latest release of pnpm! To install it, check the installation page.
Major Changes
Node.js 14 Support Discontinued
If you still require Node.js 14, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the
@pnpm/exe
package.Configuration Updates
auto-install-peers
: enabled by default.dedupe-peer-dependents
: enabled by default.resolve-peers-from-workspace-root
: enabled by default.save-workspace-protocol
: set torolling
by default.resolution-mode
: set tolowest-direct
by default.publishConfig.linkDirectory
: enabled by default.Most of the configuration changes are related to peer dependencies. Most of these settings were implemented long ago, and we recommended them to users encountering peer dependency issues. The recently added
dedupe-peer-dependents
resolved many such problems. With these new defaults, pnpm will face significantly fewer issues during migration from other package managers.Lockfile Modifications
importers
section. The newpnpm-lock.yaml
file is more resistant to git merge conflicts!resolution
object inpnpm-lock.yaml
.Other Changes
files
field in thepackage.json
, only the files that are listed in it will be deployed. The same logic is applied when injecting packages. This behaviour can be changed by setting thedeploy-all-files
setting totrue
(Related issue #5911).Migration Instructions
Before updating pnpm to v8 in your CI, regenerate your
pnpm-lock.yaml
. To upgrade your lockfile, runpnpm install
and commit the changes. Existing dependencies will not be updated; however, due to configuration changes in pnpm v8, some missing peer dependencies may be added to the lockfile and some packages may get deduplicated.You can commit the new lockfile even before upgrading Node.js in the CI, as pnpm v7 already supports the new lockfile format.
pnpm v7 Support
pnpm v7 will likely not receive any new features, but it will continue to get bug fixes for a few months and vulnerability fixes for at least a year.
Our Gold Sponsors
Our Silver Sponsors
Configuration
📅 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 has been generated by Renovate Bot.
Hi renovate!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://3317-renovate-pnpm-8-x--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
Sweet! I guess as long as this installs it should be fine!
We need to make sure the nix flake, ci and docker images all use pnpm 8 in that case, not sure if that's already the case?
True!
acb3ccb629
toc1ba3a4ef2
c1ba3a4ef2
toc3ca11b91a
c3ca11b91a
toe707c16fee
e707c16fee
to2f8dd5a3d5
2f8dd5a3d5
to2b13df795d
I created a pull request to prepare for pnpm 8. If we wait for a bit after merging that all active branches should have rebased from main / adapted the new lockfile format, which would make migration to pnpm 8 easier.
TODO
.npmrc
changes fromcb8cbc22dd
For the nix flake update we need to wait until pnpm 8 landed in nixos.
The CI and the docker image use the same image.
Adjusted the todo accordingly
2b13df795d
todfbbf5c346
Looks like the docker images are already up to date:
This failure is interesting though: https://drone.kolaente.de/vikunja/frontend/13210/1/3
dfbbf5c346
toa66703fe7d
No. I didn't rebase on top of the lockfile change branch. That's why the other branch needs to be merged first.
We should wait for a while for the most active PRs to rebase with the new lockfile.
a66703fe7d
toac3744f399
chore(deps): update pnpm to v8to wip: chore(deps): update pnpm to v8wip: chore(deps): update pnpm to v8to chore(deps): update pnpm to v8ac3744f399
toa1f8b7bf75
a1f8b7bf75
to42880176bd
42880176bd
to5bcbfa5664
chore(deps): update pnpm to v8to wip: chore(deps): update pnpm to v8wip: chore(deps): update pnpm to v8to chore(deps): update pnpm to v85bcbfa5664
to55cd2aa07d
55cd2aa07d
to1d155b4a05
I guess we can merge now. Didn't really update the other branches – but also didn't have any probs with the new format.
1d155b4a05
toc938f31935