updating_patch_dependencies_only_sprint14_#572_PR

[miqo1385]

This is a pull request!

Resolves issue #572

It was more challenging than we anticipated the last time we attempted to update the dependencies in these projects. and it appears that the job was put on hold. In order to begin moving cautiously with minor and big upgrades, I started small by changing the patch dependencies alone.
These dependencies (minor and major) need to be updated following patch updates.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@mui/[email protected]	None	+2	18.3 MB	diegoandai
npm/@mui/[email protected]	None	+2	395 kB	diegoandai
npm/@mui/[email protected]	environment	+24	10.9 MB	diegoandai
npm/@mui/[email protected]	environment	+10	761 kB	diegoandai
npm/@mui/[email protected]	environment	+22	7.37 MB	jcquintas
npm/@tanstack/[email protected]	environment	+1	2.54 MB	tannerlinsley
npm/@testing-library/[email protected]	None	+11	2.42 MB	brrianalexis, cmckinstry, dfcook, ...13 more
npm/@types/[email protected]	Transitive: environment, filesystem, unsafe	+41	1.72 MB	types
npm/@types/[email protected]	None	+1	2.36 MB	types
npm/@types/[email protected]	None	0	0 B
npm/@types/[email protected]	None	+2	1.69 MB	types
npm/[email protected]	Transitive: environment, filesystem	+41	3.93 MB	testing-library-bot
npm/[email protected]	environment, network Transitive: filesystem, shell	+17	10.5 MB	vkarpov15
npm/[email protected]	environment, network Transitive: filesystem, shell	+14	4.36 MB	balazsorban
npm/[email protected]	environment, filesystem	+3	372 kB	ai
npm/[email protected]	environment	+7	442 kB	siamahnaf
npm/[email protected]	environment Transitive: eval, filesystem, shell	+28	181 MB	lovell
npm/[email protected]	Transitive: environment, filesystem, network, shell, unsafe	+89	14.4 MB	adamwathan, malfaitrobin, reinink
npm/[email protected]	None	0	22.4 MB	typescript-bot

🚮 Removed packages: npm/@mui/[email protected], npm/@mui/[email protected], npm/@mui/[email protected], npm/@mui/[email protected], npm/@mui/[email protected], npm/@tanstack/[email protected], npm/@testing-library/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[el-riber]

here it worked very well! good job

[nhapham03]

Works on my end. LGTM!

[Asfand00]

Looks good on my end, didn't run into any issues when testing or running the server as a test.

You seem to have a check that is still pending for on pull request / build-and-test Expected part. I'm not too familiar with CI/CD stuff but I did check your .yml file for on pull request in the github workflow section and the set_status_check section is commented out. That might possibly be the issue but just guessing here, maybe try uncommenting that section to see if that fixes the issue. Otherwise, it might be another CI/CD issue. Not safe to approve yet until check is completed. I'll try to help as best I can if you need it @miqo1385.

[JesseCaddell]

In regards to the on pull request / build-and-test CI issue... I just updated the CI/CD actions yesterday. This should solve our problem. For some reason the action was not triggering. The only solution I have found so far is to make a new PR and see if it triggers. I was able to merge my changes without the build-and-test yesterday, so I'll request a second set of eyes in regards to that @bcko @taylorpapke but I am going to approve this PR once it is up to date with main! Looks good, thank you for your hard work!

[miqo1385]

Thank you Jesse, I will do a new PR for these changes.

[Diego-Cano]

Great work on the patch dependency updates! Everything looks good and runs smoothly on my end without any issues during testing. The updates are well-organized and keep things clean while addressing the patch updates effectively. I did notice that the "build-and-test" CI step is still pending. It might be worth taking another look at the .yml file, specifically the commented-out set_status_check section, to see if re-enabling that resolves the problem.

Overall, I think this is a solid update, and once the CI step is sorted, it should be good to go. Also, I found a helpful link about handling dependency updates or similar workflows : Semantic Versioning Guide for some helpful tips and best practices.