All notable changes to the Hatchet API Helm chart will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
0.18.0 - 2026-09-08
- Update the default Hatchet image to
v0.106.5for the API, setup, migration and seed Jobs.
0.17.0 - 2026-08-31
- Update the default Hatchet image to
v0.105.16for the API, setup, migration and seed Jobs.
0.16.0 - 2026-08-25
- Update the default Hatchet image to
v0.105.2for the API, setup, migration and seed Jobs.
0.15.0 - 2026-08-17
- Update the default Hatchet image to
v0.101.27for the API, setup, migration and seed Jobs.
0.14.0 - 2026-08-04
- Update the default Hatchet image to
v0.98.9for the API, setup, migration and seed Jobs.
0.13.3 - 2026-07-17
- Move the PodDisruptionBudget out of
deployment.yamlinto its ownpdb.yamltemplate, and bump it from the removedpolicy/v1beta1API version topolicy/v1. SettingpodDisruptionBudgetpreviously failed to install on Kubernetes 1.25+, wherepolicy/v1beta1no longer exists. - Propagate
image.pullSecretsto the setup,create-worker-tokenand pre-upgrade migration Job pod specs. Previously only the Deployment received them, so on a private registry the Jobs failed to pull their image and the release never bootstrapped. - Fix the PodDisruptionBudget template rendering invalid YAML when
podDisruptionBudgetsets more than one key (for examplemaxUnavailabletogether withunhealthyPodEvictionPolicy).
0.13.2 - 2026-07-16
- Automatically clean up the setup and
create-worker-tokenJobs (and their Completed pods) via a newjobTTLSecondsAfterFinishedvalue (default600), so finished bootstrap pods no longer accumulate in the namespace. Set it tonullto keep the previous behaviour of retaining finished Jobs indefinitely.
0.13.1 - 2026-07-16
- Make the Cloud SQL Auth Proxy sidecar flags configurable via
cloudSQLSidecar.args(defaults to--private-ip,--structured-logs,--port=5432);cloudSQLSidecar.addressis still appended as the final proxy argument. - Remove the hardcoded
SERVER_DEFAULT_ENGINE_VERSION=V1environment variable from the setup Job.
0.13.0 - 2026-07-14
- Updates the default Hatchet image to
v0.94.10.
0.12.4 - 2026-07-09
- Render
envFromanddeploymentEnvFromthroughtplin the deployment and setup Job templates, so secret/configmap names can reference release values (e.g.name: '{{ .Release.Name }}-postgres-secret').
0.12.3 - 2026-07-07
- Chart version bump only; no template changes in this release.
0.12.2 - 2026-07-06
- Add icon for chart
- Enable signing of chart
0.12.1 - 2026-07-05
- Added JSON schema for values
0.12.0 - 2026-06-30
- Updates the default Hatchet image to
v0.90.13.
0.11.0 - 2026-05-19
- Run database migrations as a Helm pre-upgrade hook so failed migrations block new application pods from rolling out.
- Add configurable
migrationJob.activeDeadlineSecondsandmigrationJob.backoffLimitvalues. - Retain failed migration hook Jobs by default for debugging.
- Fix setup Job template rendering invalid YAML on upgrade when both
migrationJob.enabled=true(the install-time path is skipped on upgrade) andseedJob.enabled=false: omitinitContainers:instead of emitting a bare[]at the wrong indentation. - Honor
migrationJob.activeDeadlineSecondsandmigrationJob.backoffLimiton the install-time setup Job as well; previously those values only applied to the pre-upgrade hook Job and the install-time Job used hardcoded values (15-minute ceiling).
0.10.5 - 2026-05-01
- Updates the default Hatchet image to
v0.84.0.
0.10.4 - 2026-03-11
- Updates the default Hatchet image to
v0.79.12.
0.10.3 - 2026-01-13
- Updates the default Hatchet image to
v0.74.14.
0.10.2 - 2026-01-09
- Updates the default Hatchet image to
v0.74.9.
0.10.1 - 2025-11-01
- Introduce
sharedConfig.image.tagvariable to set the same tag for all Hatchet images - Inject
.Values.deploymentEnvFromforcheck-db-connectioninit container
0.10.0 - 2025-09-22
- Use image tag
v0.71.0for all Hatchet services - Change default image
pullPolicyto beIfNotPresentfromAlways - Allow new Helm value option
deployment.extraPortsto expose extra ports such as the Prometheus metrics server - Add a new
initContainercalledcheck-db-connectionfor the setup job to check if the database is live and reachable as a first step