Bump jsonwebtoken and firebase-tools

[dependabot]

Bumps jsonwebtoken to 9.0.0 and updates ancestor dependency firebase-tools. These dependencies need to be updated together.

Updates jsonwebtoken from 8.5.1 to 9.0.0

Changelog

Sourced from jsonwebtoken's changelog.

9.0.0 - 2022-12-21

Breaking changes: See Migration from v8 to v9

Breaking changes

• Removed support for Node versions 11 and below.
• The verify() function no longer accepts unsigned tokens by default. ([834503079514b72264fd13023a3b8d648afd6a16]auth0/node-jsonwebtoken@8345030)
• RSA key size must be 2048 bits or greater. ([ecdf6cc6073ea13a7e71df5fad043550f08d0fa6]auth0/node-jsonwebtoken@ecdf6cc)
• Key types must be valid for the signing / verification algorithm

Security fixes

• security: fixes Arbitrary File Write via verify function - CVE-2022-23529
• security: fixes Insecure default algorithm in jwt.verify() could lead to signature validation bypass - CVE-2022-23540
• security: fixes Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC - CVE-2022-23541
• security: fixes Unrestricted key type could lead to legacy keys usage - CVE-2022-23539

Commits

• e1fa9dc Merge pull request from GHSA-8cf7-32gw-wr33
• 5eaedbf chore(ci): remove github test actions job (#861)
• cd4163e chore(ci): configure Github Actions jobs for Tests & Security Scanning (#856)
• ecdf6cc fix!: Prevent accidental use of insecure key sizes & misconfiguration of secr...
• 8345030 fix(sign&verify)!: Remove default none support from sign and verify met...
• 7e6a86b Upload OpsLevel YAML (#849)
• 74d5719 docs: update references vercel/ms references (#770)
• d71e383 docs: document "invalid token" error
• 3765003 docs: fix spelling in README.md: Peak -> Peek (#754)
• a46097e docs: make decode impossible to discover before verify
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by julien.wollscheid, a new releaser for jsonwebtoken since your current version.

Updates firebase-tools from 8.0.1 to 12.0.0

Release notes

Sourced from firebase-tools's releases.

v12.0.0

• Adds ext:dev:* commands to publish and manage Extensions. For step-by-step instructions on how to publish your own Extensions, see https://firebase.google.com/docs/extensions/publishers/get-started.
  • Note: These commands were previously available to early access users behind an experiment flag. There are some breaking changes from the early access version of these commands.
  • ext:dev:publish has been renamed to ext:dev:upload. ext:dev:upload defaults to uploading extensions from GitHub instead of local source.
  • ext:dev:publish is deprecated and will be removed in version 13.
  • ext:dev:delete, ext:dev:unpublish, ext:sources:create and ext:dev:emualtors:* have been removed.
• Support for Next.js i18n, basePath, and more advanced rewrites/redirects/headers (#5788)
• hosting.frameworksBackend now respects omit: true (#5788)
• Web Frameworks now memoizes framework builds for single builds across multiple hosting sites (#5788)
• Add support for Angular i18n and baseHref (#5774)
• Trip the backend requirement for Angular applications using ng-deploy w/serveOptimizedImages (#5774)
• Fixes a bug where the Storage emulator would not fall back to open rules for 'demo-' projects if firebase.json contained multiple storage targets (#5170)
• Updates firebase init function templates for TypeScript and Javascript to 2nd gen (#5775)
• Allow for atomic deployment of Hosting content & Functions rewrites via tag pinning (#5753)

v11.30.0

• Added more helpful error messages for the Firebase Hosting GitHub Action (#5749)
• Upgrade Firestore emulator to 1.17.4
• Web Frameworks will no longer try to deploy unsupported versions of NodeJS to Cloud Functions (#5733)
• Fixes bug where emulators would not start correctly due to corrupted ZIP files. (#5614, #5677)
• Adding experimental support for deploying Flutter Web applications to Firebase Hosting (#5332)
• Release Emulator Suite UI v1.11.6 (#5769)
• Adds function emulator support for v2 firestore triggers (#5685)
• Improvements for developers using Next 13's app directory (#5691)
• Resolve timeouts when bundling Next.js applications for Cloud Functions (#5691)
• Fixes bug where the functions emulator would attempt to call to prod for 'demo-' projects (#5170)
• Address issues starting the Firebase Hosting emulator with some versions of Next.js (#5781)
• Fix regex page matcher for Next.js middlewares version 1 (#5496)
• Fixes bug where functions emulator broke when client request disconnects (#5783)

v11.29.1

• Fixes a bug preventing local extension instances from being updated to uploaded versions.
• Releases firestore emulator version 1.17.3

v11.29.0

• Releases Firestore Emulator 1.17.2
  • Propagates page token from ListDocumentsResponse to GetOrListDocumentsResponse in Firestore emulator.
• Fixes an issue where Secret Manager secrets were tagged incorrectly (#5704).
• Fix bug where Custom Event channels weren't automatically crated on function deploys (#5700)
• Lift GCF 2nd gen naming restrictions (#5690)
• Fixes a bug where ext:install and ext:configure would error on extensions with no params.
• Fixed an issue with Vite and Angular integrations using a obsolete NPM command (#5710)

v11.28.0

• Adds new commands for provisioning and managing Firestore databases: (#5616)
  • firestore:databases:list
  • firestore:databases:create
  • firestore:databases:get
  • firestore:databases:update
  • firestore:databases:delete

... (truncated)

Commits

• 916138b 12.0.0
• cf799e9 Replace user of source command with (#5818)
• 6e73140 Quick fix for the frameworks integration test (#5817)
• 94a9ba3 Angular i18n, baseHref, and optimized images (#5774)
• 25fc217 Update builder image to npm 9.5 (#5816)
• 9d0d4c8 Upgrade tooling to node 18, remove explicit support for node 14 (#5730)
• b343e5d Enable the pinTags experiment by default (#5753)
• c295ed8 Handle publisher profile not found errors better. (#5813)
• 9491152 Fix link typos (#5812)
• 40c18d6 Add support for latest-approved version, and default to it instead of latest....
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.