All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- 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.
- Updated package dependencies
- Enhanced type safety for environment-specific configurations
GCP_PROJECT
environment variable added by Cloud Seed has been renamed toCLOUD_SEED_PROJECT
. Update any references to it in function code.GCP_REGION
environment variable added by Cloud Seed has been renamed toCLOUD_SEED_REGION
. Update any references to it in function code.NODE_ENV
environment variable added by Cloud Seed has been renamed toCLOUD_SEED_ENVIRONMENT
. Update any references to it in function code. Note: GCP always sets theNODE_ENV
environment variable toproduction
for deployed functions, which may affect how any NPM dependencies you have installed function.
- Environment-level function configuration overrides in
runtimeConfig
GCP_PROJECT
andNODE_ENV
environment variables are reserved in GCP and can not be set by the user
v2.1.0 - 2024-07-08
- Support for specifying timezones for cloud scheduler jobs in
runtimeConfig
v2.0.1 - 2024-06-10
- Public http functions on gen2 are now correctly exposed without authentication
v2.0.0 - 2024-06-10
- Functions will use gen2 by default and will cause any existing functions to be redeployed as gen2. To keep existing functions on gen1, add
version: "gen1"
to theruntimeConfig
.
- Support GCP Cloud Functions (2nd gen)
v1.3.0 - 2022-09-05
- The
--env
command line option is now required forcloud-seed build
. Update any pipelines to--env dev
to retain existing functionality. - GCP functions now require a runtime to be specified. Any existing functions that previously used the default value for the runtime will require
runtime: "nodejs14"
to be added to theirruntimeConfig
.
- Support for GCP Functions triggered by Cloud Tasks queues
cloud-seed build
command now requires the--env
command line option to be specified- GCP functions now require a runtime to be specified and no longer default to using Node v14
- CDKTF providers are now added as NPM dependencies and their versions are controlled in
package.json
v1.2.2 - 2022-08-16
- Fixed race condition where public permissions for functions were created before the function itself
v1.2.1 - 2022-07-19
- Added
minInstances
andmaxInstances
options toruntimeConfig
v1.2.0 - 2022-05-05
- Fixes for critical bugs introduced in 1.1.x releases
v1.1.1 - 2022-05-04
- Changed the length of VPC access connector names to comply with naming regex
v1.1.0 - 2022-04-27
- Handle conflicts with source code bucket names
v1.0.1 - 2022-04-08
- Added
retryOnFailure
option toruntimeConfig
v1.0.0 - 2022-04-04
- Initial full release