-
Notifications
You must be signed in to change notification settings - Fork 36
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
Bump deps #325
Bump deps #325
Conversation
Preview: https://packit-dashboard-pr-325.surge.sh (deployed at Mon 04 Sep 2023, 15:43 UTC) |
Build succeeded. ✔️ pre-commit SUCCESS in 1m 15s |
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.
😕
So, will the GH action for deploying PRs work without it?
(The last run went OK, but the preview is already unavailable)
yes :) actually mentioned in the commit message, but it didn't get to the PR because of multiple commits :/ |
@SpyTec shouldn't those be included only in the dev dependencies? 🤔 we got it tagged as security vulnerability from one of its dependencies (ejs) |
Yeah it could be added there, will mean less dependencies installed on prod. Luckily the attack surface for the dashboard is extremely low due to the nature of the application, so I didn't give it much thought There is one reason to have it in the dependencies and that would be if we want to build and deploy Storybook as well to try it out we'd need it in dependencies -- though no need for that atm |
Thanks a lot :) it's included in both deps and dev deps, i'll remove it from deps to counter the false-positives for now |
Signed-off-by: Matej Focko <[email protected]>
It is used only within GH Action, must've been forgotten here. Signed-off-by: Matej Focko <[email protected]>
Since we use storybooks only locally for now, move them to the development dependencies rather than dependencies required for the production run of the dashboard. AI from vulnerability report from MP+. Signed-off-by: Matej Focko <[email protected]>
Build succeeded. ✔️ pre-commit SUCCESS in 1m 30s |
as a follow-up to the vulnerability report