6 Commits (4cf7c0560db0a606c98aa73d05fab6e2999054bd)

Author	SHA1	Message	Date
Aparna Jyothi	4fc21c0d5d	npm run format	3 weeks ago
Aparna Jyothi	da434008b8	npm run format	3 weeks ago
Aparna Jyothi	af03c14274	check failure fix	4 weeks ago
Aparna Jyothi	c3e3067955	Merge remote-tracking branch 'origin/main' into node24-fix	4 weeks ago
Matthew Hughes	e75c3e80bc	Bump `form-data` to bring in fix for critical vulnerability (#618) ... The vulnerability: $ npm audit --audit-level=high # npm audit report form-data >=4.0.0 <4.0.4 || <2.5.4 Severity: critical form-data uses unsafe random function in form-data for choosing boundary - https://github.com/advisories/GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary - https://github.com/advisories/GHSA-fjxv-7rqg-78g4 fix available via `npm audit fix` node_modules/@azure/core-http/node_modules/form-data node_modules/@types/node-fetch/node_modules/form-data node_modules/form-data 1 critical severity vulnerability To address all issues, run: npm audit fix This change is the result of from running `npm audit fix` and then using[1] to update licenses via `licensed cache`. It doesn't look like `dependabot` previously raised any PRs for this dependency, so this bumps it from `4.0.0` to `4.0.4`, see the changelog[2] for details. Link: https://github.com/licensee/licensed [1] Link: https://github.com/form-data/form-data/blob/v4.0.4/CHANGELOG.md [2]	4 weeks ago
Aparna Jyothi	b184a007c8	fix for check failures	4 weeks ago