Chore/update nanoid - #3356
Chore/update nanoid#3356andrewkim099 wants to merge 1 commit into
Conversation
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Andrew Kim seems not to be a GitHub user. Have you signed the CLA already but the status is still pending? Recheck it. |
1 similar comment
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Andrew Kim seems not to be a GitHub user. Have you signed the CLA already but the status is still pending? Recheck it. |
Bump the E2E test dependency from ^5.0.9 to ^5.1.11. Refresh the lockfile to resolve nanoid 5.1.16 and update the transitive nanoid 3.x resolution from 3.3.11 to 3.3.12. ✅ Closes: SECVULN-57182
4fd0c8a to
6eef36f
Compare
Description
Bump the E2E dependency to ^5.1.11 and refresh the lockfile resolutions
How to test
To test which version is installed locally run pnpm --filter e2e-tests list nanoid --depth 0
Checklist
- [ ] I have added before and after screenshots for UI changes- [ ] I have added JSON response output for API changes- [ ] I have added steps to reproduce and test for bug fixes in the description- [ ] I have commented on my code, particularly in hard-to-understand areas- [ ] I have addeda11y-testslabel to run a11y audit tests if neededPCI review checklist
- [ ] If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.- [ ] If applicable, I've documented the impact of any changes to security controls.Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.