Skip to content

Releases: cloudfoundry/cf-deployment

v40.7.0

26 Apr 11:11
Compare
Choose a tag to compare

Notices

⚠️ The routing-release 0.296.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Release Updates

Warning: The Release Notes column only highlights noteworthy updates for each release bump. However, it is not exhaustive and we recommend you visit the actual release notes below before every upgrade.

Release Old Version New Version Release Notes
capi 1.179.0 1.180.0
credhub 2.12.71 2.12.72
cflinuxfs4 1.94.0 1.95.0
pxc 1.0.26 1.0.27
cflinuxfs4-compat 1.94.0 1.95.0
mapfs 1.2.67 1.2.68
nfs-volume 7.1.62 7.1.63
haproxy 13.4.0+2.8.5 13.5.0+2.8.9
smb-volume 3.1.65 3.1.66
backup-and-restore-sdk 1.19.11 1.19.12

v40.6.0

22 Apr 13:58
Compare
Choose a tag to compare

Notices

⚠️ The routing-release 0.296.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Release Updates

Warning: The Release Notes column only highlights noteworthy updates for each release bump. However, it is not exhaustive and we recommend you visit the actual release notes below before every upgrade.

Release Old Version New Version Release Notes
credhub 2.12.69 2.12.71
cflinuxfs4 1.92.0 1.94.0
cf-smoke-tests 42.0.141 42.0.142
php-buildpack 4.6.17 4.6.18
nodejs-buildpack 1.8.23 1.8.24
r-buildpack 1.2.10 1.2.11
python-buildpack 1.8.22 1.8.23
metric-store 1.6.0 1.6.1
cflinuxfs4-compat 1.92.0 1.94.0
mapfs 1.2.66 1.2.67
smb-volume 3.1.64 3.1.65

v40.5.0

18 Apr 10:28
Compare
Choose a tag to compare

Notices

⚠️ The routing-release 0.296.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Release Updates

Warning: The Release Notes column only highlights noteworthy updates for each release bump. However, it is not exhaustive and we recommend you visit the actual release notes below before every upgrade.

Release Old Version New Version Release Notes
binary-buildpack 1.1.10 1.1.11
cf-networking 3.45.0 3.46.0
capi 1.177.0 1.179.0
cflinuxfs4 1.89.0 1.92.0
java-buildpack 4.67.0 4.68.0
go-buildpack 1.10.17 1.10.18
garden-runc 1.51.0 1.52.0
dotnet-core-buildpack 2.4.26 2.4.27
diego 2.97.0 2.98.0
nginx-buildpack 1.2.12 1.2.13
nats 56.18.0 56.19.0
staticfile-buildpack 1.6.11 1.6.12
silk 3.45.0 3.46.0
ruby-buildpack 1.10.11 1.10.13
routing 0.295.0 0.296.0
loggregator-agent 8.0.2 8.1.0
syslog 12.2.4 12.2.5
backup-and-restore-sdk 1.19.10 1.19.11
windows2019fs 2.65.0 2.66.0
cflinuxfs4-compat 1.89.0 1.92.0
envoy-nginx 0.24.0 0.25.0
nfs-volume 7.1.61 7.1.62
windowsfs 2.65.0 2.66.0

v40.4.0

15 Apr 09:13
Compare
Choose a tag to compare

Notices

⚠️ The routing-release 0.295.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Release Updates

Warning: The Release Notes column only highlights noteworthy updates for each release bump. However, it is not exhaustive and we recommend you visit the actual release notes below before every upgrade.

Release Old Version New Version Release Notes
capi 1.176.0 1.177.0
credhub 2.12.67 2.12.69
cflinuxfs4 1.87.0 1.89.0
nats 56.16.0 56.18.0
loggregator 107.0.13 107.0.14
uaa 77.4.0 77.5.0
statsd-injector 1.11.39 1.11.40
system-metrics-scraper 4.0.7 4.0.8
system-metrics 3.0.6 3.0.7
otel-collector 0.4.0 0.4.1
smb-volume 3.1.63 3.1.64
cflinuxfs4-compat 1.88.0 1.89.0
winc 2.22.0 2.23.0
hwc-buildpack 3.1.35 3.1.36
syslog 12.2.3 12.2.4
mapfs 1.2.65 1.2.66
nfs-volume 7.1.60 7.1.61
windowsfs 2.64.0 2.65.0
windows2019fs 2.64.0 2.65.0

v40.3.0

09 Apr 06:26
Compare
Choose a tag to compare

Notices

⚠️ The credhub-release 2.12.67 might fail to start if CredHub is configured with a database vendor that enforces additional access control on database triggers creation (e.g. Amazon RDS), as this release will attempt to create database triggers at start time. This issue is still under investigation. We recommend that you do not use this release if you are using vendors like Amazon RDS. Upgrading to credhub-release 2.12.70 is advised. ⚠️
⚠️ The routing-release 0.295.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Release Updates

Warning: The Release Notes column only highlights noteworthy updates for each release bump. However, it is not exhaustive and we recommend you visit the actual release notes below before every upgrade.

Release Old Version New Version Release Notes
capi 1.175.0 1.176.0
bpm 1.2.17 1.2.18
cflinuxfs4 1.86.0 1.87.0
cf-smoke-tests 42.0.140 42.0.141
pxc 1.0.25 1.0.26
routing 0.294.0 0.295.0
backup-and-restore-sdk 1.19.9 1.19.10
mapfs 1.2.64 1.2.65
nfs-volume 7.1.59 7.1.60
cflinuxfs4-compat 1.86.0 1.88.0
smb-volume 3.1.62 3.1.63

v40.2.0

08 Apr 22:29
Compare
Choose a tag to compare

Notices

⚠️ The routing-release 0.294.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Stemcell Updates

Release Old Version New Version
ubuntu-jammy 1.406 1.423
stemcell-only

v40.1.0

03 Apr 11:56
Compare
Choose a tag to compare

Notices

⚠️ The routing-release 0.294.0 contains a known issue: gorouter will no longer present the most specific certificate match but rather the first certificate that matches. Upgrading to routing-release 0.295.0 is advised. ⚠️
⚠️ The credhub-release 2.12.67 might fail to start if CredHub is configured with a database vendor that enforces additional access control on database triggers creation (e.g. Amazon RDS), as this release will attempt to create database triggers at start time. This issue is still under investigation. We recommend that you do not use this release if you are using vendors like Amazon RDS. Upgrading to credhub-release 2.12.70 is advised. ⚠️
⚠️ The routing-release 0.294.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Release Updates

Warning: The Release Notes column only highlights noteworthy updates for each release bump. However, it is not exhaustive and we recommend you visit the actual release notes below before every upgrade.

Release Old Version New Version Release Notes
cflinuxfs4 1.83.0 1.86.0
diego 2.96.0 2.97.0
nats 56.15.0 56.16.0
pxc 1.0.24 1.0.25
uaa 77.3.0 77.4.0
smb-volume 3.1.61 3.1.62
cflinuxfs4-compat 1.83.0 1.86.0
mapfs 1.2.63 1.2.64
nfs-volume 7.1.58 7.1.59
backup-and-restore-sdk 1.19.8 1.19.9

v40.0.0

26 Mar 07:34
Compare
Choose a tag to compare

Notices

⚠️ The routing-release 0.294.0 contains a known issue: gorouter will no longer present the most specific certificate match but rather the first certificate that matches. Upgrading to routing-release 0.295.0 is advised. ⚠️
⚠️ The credhub-release 2.12.67 might fail to start if CredHub is configured with a database vendor that enforces additional access control on database triggers creation (e.g. Amazon RDS), as this release will attempt to create database triggers at start time. This issue is still under investigation. We recommend that you do not use this release if you are using vendors like Amazon RDS. Upgrading to credhub-release 2.12.70 is advised. ⚠️
⚠️ The routing-release 0.294.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Manifest Updates

The cloud controller configuration option legacy_md5_buildpack_paths_enabled is now set to false by default.

Ops-files

Deleted Ops-files

⚠️ The ops file operations/experimental/fips-compliance.yml has been deleted.

Release Updates

Warning: The Release Notes column only highlights noteworthy updates for each release bump. However, it is not exhaustive and we recommend you visit the actual release notes below before every upgrade.

Release Old Version New Version Release Notes
cf-smoke-tests 42.0.139 42.0.140
cf-networking 3.44.0 3.45.0
diego 2.95.0 2.96.0
credhub 2.12.66 2.12.67
garden-runc 1.50.0 1.51.0
routing 0.293.0 0.294.0
silk 3.44.0 3.45.0
backup-and-restore-sdk 1.19.7 1.19.8
smb-volume 3.1.60 3.1.61
mapfs 1.2.62 1.2.63
winc 2.21.0 2.22.0

v39.8.0

21 Mar 15:20
Compare
Choose a tag to compare

Notices

⚠️ The routing-release 0.293.0 contains a known issue: gorouter will no longer present the most specific certificate match but rather the first certificate that matches. Upgrading to routing-release 0.295.0 is advised. ⚠️
⚠️ The routing-release 0.293.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Release Updates

Warning: The Release Notes column only highlights noteworthy updates for each release bump. However, it is not exhaustive and we recommend you visit the actual release notes below before every upgrade.

Release Old Version New Version Release Notes
cflinuxfs4 1.82.0 1.83.0
cf-smoke-tests 42.0.137 42.0.139
dotnet-core-buildpack 2.4.25 2.4.26
r-buildpack 1.2.9 1.2.10
php-buildpack 4.6.16 4.6.17
python-buildpack 1.8.21 1.8.22
ruby-buildpack 1.10.10 1.10.11
uaa 77.2.0 77.3.0
backup-and-restore-sdk 1.19.4 1.19.7
cflinuxfs4-compat 1.82.0 1.83.0
smb-volume 3.1.59 3.1.60
windows2019fs 2.63.0 2.64.0
nfs-volume 7.1.57 7.1.58
windowsfs 2.63.0 2.64.0

v39.7.0

18 Mar 20:16
Compare
Choose a tag to compare

Notices

⚠️ The routing-release 0.293.0 contains a known issue: for request/response workflows using Expect: 100-continue to delay POST data until the backend issues a 100 continue, gorouter incorrectly returns an 200 OK status code to the client, regardless of what final status code the backend set (e.g. 401, 502, 203 all appear as 200 to the client). HTTP Access logs + Gorouter HTTP request metrics showed the correct status codes. Upgrading to routing-release 0.297.0 is advised. ⚠️

Stemcell Updates

Release Old Version New Version
ubuntu-jammy 1.404 1.406
stemcell-only