chore(deps): update dependency firebase-functions-test to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
firebase-functions-test	0.3.3 -> 3.3.0

---

Release Notes

firebase/firebase-functions-test (firebase-functions-test)

v3.3.0

Compare Source

• Add support for v2 callable functions (#​229).

v3.2.0

Compare Source

• Add support for testing Firestore 2nd gen Auth Context triggers. (#​227)

v3.1.1

Compare Source

• Extend support for firebase-admin@12 (#​220)

v3.1.0

Compare Source

• Add testing support for 2nd gen firestore triggers (#​200).

v3.0.0

Compare Source

BREAKING

• Drop support for Firebase Functions SDK v3 and below.
• Drop support for Firebase Admin SDK v7 and below.

v2.4.0

Compare Source

• Add support for Params (#​168)
• Use conditional typing for defining the right set of options (#​166)
• Bump ts-deepmerge from 2.0.1 to 2.0.2 (#​161)

v2.3.0

Compare Source

• Add MockCloudEvents for RTDB-V2 (#​156)
• Update Rtdb test sdk to allow json for Mock CloudEvents (#​159)

v2.2.0

Compare Source

• Add >=jest@28 as a peerDependency (#​152)

v2.1.0

Compare Source

Breaking Improvements

• Generated CloudEvents will use the user-provided Partial to infer other fields. #​146
  • For storage events, updating the Partial's bucket will update:
    • data.bucket
    • Parts of source, data.selfLink, data.id
  • For PubSub events, updating the Partial's data.message.json will:
    • generate a new base64 string for data.message.data
      • (But a user-provided data.message.data still takes priority)

Full list of Changes

• Update to README.md to include more samples #​143
• Add top-level bucket field to Mock Storage CloudEvents #​145
• Delete .travis.yml #​120
• Add CI for firebase-functions-test #​147
• Refactor MockCloudEvent generation to include user partial #​146
• Unit tests for MockCloudEvent generation refactor #​150
• Updated Dependencies
  • Bump plist from 3.0.1 to 3.0.5 #​132
  • Bump minimist from 1.2.5 to 1.2.6 #​129
  • Bump path-parse from 1.0.6 to 1.0.7 #​115
  • Bump pathval from 1.1.0 to 1.1.1 #​127
  • Bump glob-parent from 5.1.1 to 5.1.2 #​103
  • Bump ws from 7.3.1 to 7.5.7 #​133

v2.0.2

Compare Source

• Fix Compiler error after update to v2.0.0 (#​141)

v2.0.1

Compare Source

• Make WrappedFunction curry type info (#​138)
• Update to [email protected] to include updated typing (#​139)

v2.0.0

Compare Source

• Try to extract context.params from triggered data pull request
• Implement firebase-functions-test wrapV2 pull request
• Update minimum Node version to v14 pull request

---

Configuration

📅 Schedule: Branch creation - "on saturday" in timezone Asia/Tokyo, 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 this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.