-
-
Notifications
You must be signed in to change notification settings - Fork 254
chore: bump eslint, node and cross dependencys #1789
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.
Files not reviewed (1)
- martin/martin-ui/package.json: Language not supported
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks! At some point we should rework CI a bit so it can auto-merge demo things without admin approval - i.e. make it so that the final CI task would pass if dependent jobs are skipped
"fnm default 22", | ||
# verify installation | ||
"node --version", | ||
"npm --version", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to bump node to next major as required by eslint.
Bumping node requires newer libc requiring cross update.
But npm is still not quite installed in the next step (in the build script). Unsure where this is breaking apart.
Will need to look into how cross is really working.
maybe a symlink is missing, maybe more.
Our frontend dependency on
eslint
is a bit dated. This PR migrates them to newer versions.Eslint was changed to their new configuration format.
Bumping
eslint
requires bumpingnode
requires bumpingcross
(due to libc)Splitting this into this and #1792 is likey a good idea