v3.0.2

What's Changed

• Add support for specifying event filters by @sethvargo in #417
• Release: v3.0.2 by @google-github-actions-bot in #418

Full Changelog: v3.0.1...v3.0.2

v3

Floating v3 release

v3.0.1

What's Changed

• Remove features that were upstreamed into actions-utils by @sethvargo in #412
• Update inputs to be consistent by @sethvargo in #414
• Release: v3.0.1 by @google-github-actions-bot in #415

Full Changelog: v3.0.0...v3.0.1

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: v2.1.0...v3.0.0

v2.1.0

What's Changed

• Update README and CI to use latest version by @sethvargo in #400
• Update README.md by @jehan60188 in #401
• Update README.md by @sethvargo in #402
• Update deps by @sethvargo in #404
• Release: v2.1.0 by @google-github-actions-bot in #405

New Contributors

• @jehan60188 made their first contribution in #401

Full Changelog: v2...v2.1.0

v2

Floating v2 alias

v2.0.0

⚠️ This version requires Node 20 or later!

What's Changed

• dependabot: only do security updates by @sethvargo in #387
• update all deps by @sethvargo in #388
• Spelling fix in README by @therefromhere in #389
• Update deps to Node 20 by @sethvargo in #393
• Add CI for release branches by @sethvargo in #395
• Release: v2.0.0 by @google-github-actions-bot in #398

New Contributors

• @therefromhere made their first contribution in #389

Full Changelog: v1...v2.0.0

v0.11.0

⚠️ This version is no longer supported!

v0

⚠️ This version is no longer supported!

Floating v0 alias

v1.0.1

What's Changed

• Update CI and deps by @sethvargo in #367
• Handle 404 vs other errors when getting the Cloud Function by @sethvargo in #368
• Improve cleanup script by @sethvargo in #369
• Update Readme with ingress_settings valid inputs by @m3h0w in #370
• Update README.md by @juanmanuelramallo in #372
• chore: update dependencies (automated) by @verbanicm in #375
• Switch to pull non-secret values from env by @sethvargo in #376
• Give possible values for memory_mb by @greg-finley in #377
• Add support info by @sethvargo in #380
• chore: update dependencies (automated) by @verbanicm in #382
• Release: v1.0.1 by @google-github-actions-bot in #383

New Contributors

• @m3h0w made their first contribution in #370
• @juanmanuelramallo made their first contribution in #372
• @greg-finley made their first contribution in #377

Full Changelog: v1.0.0...v1.0.1