You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I start this thread to discuss the future of Creedengo JavaScript 🚀
I have planned to release a new major version of the plugin this summer with the following minimum requirements:
SonarQube community version: 10.x
SonarQube server version: 2025.1 LTA
ESLint version: 8+
Node.js version: 20.x, 22+ (14.x, 16.x and 18.x will be end of life)
Are there any objections to these changes? They'll make it possible to keep up with the ecosystem, while leaving ESLint users acceptable room to migrate progressively (v8 still supported). Regarding SonarQube, I'll wait for SonarQube 9.9 LTA to reach the end of its life before changing the prerequisites, which should happen in July 2025 (see release cycle here).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I start this thread to discuss the future of Creedengo JavaScript 🚀
I have planned to release a new major version of the plugin this summer with the following minimum requirements:
Are there any objections to these changes? They'll make it possible to keep up with the ecosystem, while leaving ESLint users acceptable room to migrate progressively (v8 still supported). Regarding SonarQube, I'll wait for SonarQube 9.9 LTA to reach the end of its life before changing the prerequisites, which should happen in July 2025 (see release cycle here).
Beta Was this translation helpful? Give feedback.
All reactions