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

Upgrade to pnpm@8; drop support for Node.js 14 (OSOE-603) #42

Closed
0liver opened this issue Mar 29, 2023 · 1 comment · Fixed by #58
Closed

Upgrade to pnpm@8; drop support for Node.js 14 (OSOE-603) #42

0liver opened this issue Mar 29, 2023 · 1 comment · Fixed by #58
Assignees

Comments

@0liver
Copy link
Contributor

0liver commented Mar 29, 2023

This should be done once we've upgraded all internal projects and developers to Node.js 16, at least.

There's at least one catch, though. Citing the v8.0.0 release notes:

A lockfile is generated even for projects with no dependencies.

Also, we should wait a bit until at least a few bug fixes have been incorporated.

Jira issue

@github-actions github-actions bot changed the title Upgrade to pnpm@8; drop support for Node.js 14 Upgrade to pnpm@8; drop support for Node.js 14 (OSOE-603) Mar 29, 2023
@Piedone
Copy link
Member

Piedone commented May 22, 2023

Together with this, the NE reference in Lombiq.Tests.UI also needs to be removed, because that's also only there for PNPM 7 compatibility during NuGet publishing.

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 a pull request may close this issue.

3 participants