Releases: cloudfoundry/cf-deployment
v40.3.0
Notices
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
Notices
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
Notices
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
Notices
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
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
Notices
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
Notices
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 |
v39.6.0
Notices
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.173.0 | 1.175.0 | |
| credhub | 2.12.65 | 2.12.66 | |
| cflinuxfs4 | 1.81.0 | 1.82.0 | |
| loggregator | 107.0.12 | 107.0.13 | |
| statsd-injector | 1.11.38 | 1.11.39 | |
| loggregator-agent | 8.0.1 | 8.0.2 | |
| windows2019 | 2019.70 | 2019.71 | |
| otel-collector | 0.3.2 | 0.4.0 | |
| system-metrics-scraper | 4.0.6 | 4.0.7 | |
| system-metrics | 3.0.5 | 3.0.6 | |
| syslog | 12.2.2 | 12.2.3 | |
| mapfs | 1.2.61 | 1.2.62 | |
| nfs-volume | 7.1.56 | 7.1.57 | |
| cflinuxfs4-compat | 1.81.0 | 1.82.0 | |
| smb-volume | 3.1.58 | 3.1.59 |
v39.5.0
Notices
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.390 | 1.404 |
| stemcell-only |
v39.4.0
Notices
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 |
|---|---|---|---|
| bpm | 1.2.16 | 1.2.17 | |
| binary-buildpack | 1.1.9 | 1.1.10 | |
| credhub | 2.12.64 | 2.12.65 | |
| cflinuxfs4 | 1.79.0 | 1.81.0 | |
| cf-smoke-tests | 42.0.134 | 42.0.137 | |
| cf-networking | 3.43.0 | 3.44.0 | |
| dotnet-core-buildpack | 2.4.24 | 2.4.25 | |
| java-buildpack | 4.66.0 | 4.67.0 | |
| go-buildpack | 1.10.16 | 1.10.17 | |
| php-buildpack | 4.6.15 | 4.6.16 | |
| nodejs-buildpack | 1.8.22 | 1.8.23 | |
| r-buildpack | 1.2.8 | 1.2.9 | |
| nginx-buildpack | 1.2.11 | 1.2.12 | |
| staticfile-buildpack | 1.6.10 | 1.6.11 | |
| silk | 3.43.0 | 3.44.0 | |
| ruby-buildpack | 1.10.9 | 1.10.10 | |
| routing | 0.292.0 | 0.293.0 | |
| python-buildpack | 1.8.20 | 1.8.21 | |
| uaa | 77.1.0 | 77.2.0 | |
| log-cache | 3.0.10 | 3.0.11 | |
| cf-cli | 1.60.0 | 1.63.0 | |
| smb-volume | 3.1.57 | 3.1.58 | |
| backup-and-restore-sdk | 1.19.3 | 1.19.4 | |
| mapfs | 1.2.59 | 1.2.61 | |
| nfs-volume | 7.1.55 | 7.1.56 | |
| cflinuxfs4-compat | 1.79.0 | 1.81.0 |
v39.3.0
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 |
|---|---|---|---|
| diego | 2.94.0 | 2.95.0 | |
| credhub | 2.12.63 | 2.12.64 | |
| cflinuxfs4 | 1.75.0 | 1.79.0 | |
| cf-smoke-tests | 42.0.133 | 42.0.134 | |
| cf-cli | 1.59.0 | 1.60.0 | |
| cflinuxfs4-compat | 1.74.0 | 1.79.0 | |
| backup-and-restore-sdk | 1.19.2 | 1.19.3 | |
| mapfs | 1.2.58 | 1.2.59 | |
| nfs-volume | 7.1.54 | 7.1.55 | |
| smb-volume | 3.1.56 | 3.1.57 |