⬆️ Bump google-github-actions/deploy-cloud-functions from 2.1.0 to 3.0.0

[dependabot]

Bumps google-github-actions/deploy-cloud-functions from 2.1.0 to 3.0.0.

Release notes

Sourced from google-github-actions/deploy-cloud-functions's releases.

v3.0.0

Notable Changes

While we always seek to minimize breaking changes, there is a substantial delta between Cloud Functions v1 and Cloud Functions v2, such that the GitHub Action was mostly rewritten.

• "v3" supports 2nd generation Cloud Functions (GEN_2). 1st generation Cloud Functions may work, but GEN_1 is not supported. Use google-github-actions/deploy-cloud-functions@v2 for 1st generation functions.

• "files" inputs such as environment_variables_file have been removed. To source values from a file, read the file in a prior step and set an output. There are many community-sponsored GitHub Actions that provide this functionality.

• "memory" is now specified as a string with a suffix (e.g. "5Mb") instead of assuming megabytes.

• "secret_env_vars" and "secret_volumes" have been combined into a single "secrets" input which accepts environment variable keys or filepaths.

• Various fields were renamed to match the "v2" API, such as "service_account" and "min/max_instance_count".

• Labels, environment variables, and secrets are still declarative, but they are not modified if no values are given. You can explicitly empty the value by setting the input to the literal string "{}".

• Functions are only served over HTTPS (no HTTP). This is a requirement for Cloud Functions v2.

• Since Cloud Functions v2 uses EventArc, you may need to enable the EventArc API and re-configure triggers (many inputs have changed to match the new API specification).

In accordance with our support policy, when "v3" is released as GA, we will stop supporting "v1" and continue to support "v2" and "v3".

Full Changelog: google-github-actions/deploy-cloud-functions@v2.1.0...v3.0.0

Commits

• 8a1e165 Release: v3.0.0-beta1 (#411)
• a5b186d Switch to gen2 API (#409)
• 6282b54 security: bump undici from 5.28.3 to 5.28.4 (#408)
• be8d802 security: bump undici from 5.28.2 to 5.28.3 (#406)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.