nextcloud: update node to v20 #8
Merged
Conversation
This file contains 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
|
I thought there wasn't a release with that fix published, yet but if that already works it's lovely. One less patch I need to carry around. |
SuperSandro2000
changed the title
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.
Resolves the issue of nodejs_16 being EOL upstream in nixpkgs
It seems while nextcloud/recognize#985 is open and possibly being worked on upstream in recognize, a user can work around this via the built-in option to define node location (the use of path will obviously be fragile here to nixpkgs updates, but for now it's working in my testing)
Current settings as per:
/settings/admin/recognizeHappy to wait for upstream to resolve this with said, if that is the preference 👍