v4.1.0

Added

• Added cloud-seed run command to run functions locally with automatic rebuilding on changes. See README.md for documentation on how to use this command.
• Cloud Seed commands can now discover the cloudseed.json configuration file for the project when run from within a subdirectory.

Fixed

• Fixed an "Invalid value" error when deploying scheduledJob functions with attemptDeadline option set to the default value.

v4.0.0

v4.0.0

Breaking changes

• The package no longer supports deprecated Node.js engine versions. Upgrade your project to Node.js v20 or later.
• Esbuild, which is used to build and bundle the source code for functions, has been upgraded through several breaking versions. Ensure you complete full regression testing of your functions after upgrading.

Changed

• Updated package dependencies
• Enhanced type safety for environment-specific configurations

v3.0.0

Breaking changes

• GCP_PROJECT environment variable added by Cloud Seed has been renamed to CLOUD_SEED_PROJECT. Update any references to it in function code.
• GCP_REGION environment variable added by Cloud Seed has been renamed to CLOUD_SEED_REGION. Update any references to it in function code.
• NODE_ENV environment variable added by Cloud Seed has been renamed to CLOUD_SEED_ENVIRONMENT. Update any references to it in function code. Note: GCP always sets the NODE_ENV environment variable to production for deployed functions, which may affect how any NPM dependencies you have installed function.

Added

• Environment-level function configuration overrides in runtimeConfig

Fixed

• GCP_PROJECT and NODE_ENV environment variables are reserved in GCP and can not be set by the user

Full Changelog: v2.1.0...v3.0.0

v2.1.0

Cloud seed v2.1.0 out:

This introduces support for specifying timezones for cloud scheduler jobs. This can be added via runtimeConfig and needs to be in the format as per https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

v1.4.0

1.4.0

v2.0.1-alpha1

2.0.1-alpha1

v2.0.1-alpha

2.0.1-alpha

v2.0.1

Ensuring public http functions are publicly exposed and don't require authentication

v2.0.0

Official support for Gen 2 cloud functions

Breaking change: Gen 2 cloud functions to be used by default. If you plan on upgrading to this version and want to continue using gen1 functions, please set "version" to "gen1" in the runtimeConfig for your cloud function

v1.4.5-alpha

Remove "scheduled-" prefix from pub sub topic name on event type.