chore(deps): update dependency uuid to v9

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
uuid	^8.0.0 -> ^9.0.0

---

Release Notes

uuidjs/uuid

v9.0.0

Compare Source

⚠ BREAKING CHANGES

• Drop Node.js 10.x support. This library always aims at supporting one EOLed LTS release which by this time now is 12.x which has reached EOL 30 Apr 2022.

• Remove the minified UMD build from the package.

  Minified code is hard to audit and since this is a widely used library it seems more appropriate nowadays to optimize for auditability than to ship a legacy module format that, at best, serves educational purposes nowadays.

  For production browser use cases, users should be using a bundler. For educational purposes, today's online sandboxes like replit.com offer convenient ways to load npm modules, so the use case for UMD through repos like UNPKG or jsDelivr has largely vanished.

• Drop IE 11 and Safari 10 support. Drop support for browsers that don't correctly implement const/let and default arguments, and no longer transpile the browser build to ES2015.

  This also removes the fallback on msCrypto instead of the crypto API.

  Browser tests are run in the first supported version of each supported browser and in the latest (as of this commit) version available on Browserstack.

Features

• optimize uuid.v1 by 1.3x uuid.v4 by 4.3x (430%) (#​597) (3a033f6)
• remove UMD build (#​645) (e948a0f), closes #​620
• use native crypto.randomUUID when available (#​600) (c9e076c)

Bug Fixes

• add Jest/jsdom compatibility (#​642) (16f9c46)
• change default export to named function (#​545) (c57bc5a)
• handle error when parameter is not set in v3 and v5 (#​622) (fcd7388)
• run npm audit fix (#​644) (04686f5)
• upgrading from uuid3 broken link (#​568) (1c849da)

build

• drop Node.js 8.x from babel transpile target (#​603) (aa11485)

• drop support for legacy browsers (IE11, Safari 10) (#​604) (0f433e5)

• drop node 10.x to upgrade dev dependencies (#​653) (28a5712), closes #​643

8.3.2 (2020-12-08)

Bug Fixes

• lazy load getRandomValues (#​537) (16c8f6d), closes #​536

8.3.1 (2020-10-04)

Bug Fixes

• support expo>=39.0.0 (#​515) (c65a0f3), closes #​375

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[Shnatsel]

I've reviewed the changelog for uuid and the changes look good to me.

However, CI is failing for Data Catalog, Cloud Functions and Healthcare:

Error: google-github-actions/auth failed with: retry function failed after 1 attempt: gitHub Actions did not inject $ACTIONS_ID_TOKEN_REQUEST_TOKEN or $ACTIONS_ID_TOKEN_REQUEST_URL into this job. This most likely means the GitHub Actions workflow permissions are incorrect, or this job is being run from a fork. For more information, please see https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token

We'll need someone familiar with those products to take a look.

[kweinmeister]

FYI @Shnatsel That error is expected for dependency updates from a fork, rather than a branch. We can ignore failures that are of type pull_request only if the matching pull_request_target for that same service is passing.

There is an open issue to clean up the GitHub Actions workflow logic, so only the PR target check triggers in this scenario.

[Shnatsel]

I see, thank you for clarifying. All pull_request_target checks are passing.

[dpebot]

/gcbrun