We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
package.json
The package.json is fixed
It seems we have broken package.json in a way that throws Dependabot off: https://github.com/FriendsOfTYPO3/tea/network/updates/886067788
Dependabot failed to update your dependencies because there was an error resolving your JavaScript dependency files. Dependabot encountered the following error: Dependabot uses Node.js v20.17.0 and NPM 10.8.2. Due to the engine-strict setting, the update will not succeed.
Dependabot failed to update your dependencies because there was an error resolving your JavaScript dependency files.
Dependabot encountered the following error:
Dependabot uses Node.js v20.17.0 and NPM 10.8.2. Due to the engine-strict setting, the update will not succeed.
The text was updated successfully, but these errors were encountered:
We'll probably need to allow Node.js 20 in package.json as well to unbreak Dependabot.
Sorry, something went wrong.
Fixed by #1457.
Reopening as Dependabot still has problems:
https://github.com/FriendsOfTYPO3/tea/network/updates/886128238 Dependabot uses Node.js v20.17.0 and NPM 10.8.2. Due to the engine-strict setting, the update will not succeed.
No, still not solved: https://github.com/FriendsOfTYPO3/tea/network/updates/886222075
Reopening.
We should find out what this "engine-strict setting" is and how to work with it.
linxpinx
Successfully merging a pull request may close this issue.
Goal
The package.json is fixed
Acceptance criteria
Additional information
It seems we have broken package.json in a way that throws Dependabot off:
https://github.com/FriendsOfTYPO3/tea/network/updates/886067788
The text was updated successfully, but these errors were encountered: