Oskar-Bonde opened a new issue, #33881:
URL: https://github.com/apache/superset/issues/33881

   ### Bug description
   
   It is currently not possible to run `npm ci` in Superset 4.1.0, 4.1.1 and 
4.1.2. The following error is raised:
   "Invalid: lock file's luxon@3.5.0 does not satisfy luxon@3.6.1"
   
   `npm ci` worked fine 2025-06-19, but has not worked since 2025-06-23. 
   
   Running `npm install` bumps luxon to 3.6.1, after which `npm ci` works fine.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   4.1.2
   
   ### Python version
   
   3.10
   
   ### Node version
   
   18 or greater
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   I've tested this on branches 4.1.0, 4.1.1 and 4.1.2. No code changes made.
   
   Full error message:
   ```
   npm ERR! code EUSAGE
   npm ERR!
   npm ERR! `npm ci` can only install packages when your package.json and 
package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock 
file with `npm install` before continuing.
   npm ERR!
   npm ERR! Invalid: lock file's luxon@3.5.0 does not satisfy luxon@3.6.1
   ```
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to