v3.0.7

What's Changed

• feat: new release process by @verbanicm in #443
• fix: add bot token for release by @verbanicm in #444
• Release: v3.0.7 by @google-github-actions-bot in #445

Full Changelog: v3.0.6...v3.0.7

v3

Floating v3 release

v3.0.6

Important

This is an invalid release caused by errors in new release process.

What's Changed

• feat: add publish workflow by @verbanicm in #436
• Release: v3.0.6 by @google-github-actions-bot in #437
• fix: publish and release process by @verbanicm in #438
• fix: downgrade version by @verbanicm in #439
• Release: v3.0.6 by @google-github-actions-bot in #440
• fix: release and publish by @verbanicm in #441
• Release: v3.0.6 by @google-github-actions-bot in #442

Full Changelog: v3.0.5...v3.0.6

v3.0.5

What's Changed

• Fix package name by @sethvargo in #428
• Fix updateMask computing too deep by @sethvargo in #430
• Release: v3.0.5 by @google-github-actions-bot in #431

Full Changelog: v3.0.4...v3.0.5

v3.0.4

What's Changed

• Fix fieldMask and add more debug output by @sethvargo in #424
• Update deps by @sethvargo in #426
• Release: v3.0.4 by @google-github-actions-bot in #427

Full Changelog: v3.0.3...v3.0.4

v3.0.3

What's Changed

• Remove legacy event_trigger_service input by @sethvargo in #420
• Release: v3.0.3 by @google-github-actions-bot in #422

Full Changelog: v3.0.2...v3.0.3

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.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