Releases: cloudfoundry/cf-deployment
v40.17.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 |
|---|---|---|---|
| capi | 1.182.0 | 1.183.0 | |
| bpm | 1.2.19 | 1.2.20 | |
| cf-smoke-tests | 42.0.148 | 42.0.149 | |
| credhub | 2.12.76 | 2.12.77 | |
| php-buildpack | 4.6.19 | 4.6.20 | |
| routing | 0.298.0 | 0.300.0 | |
| log-cache | 3.0.11 | 3.1.0 | |
| mapfs | 1.2.72 | 1.2.79 | |
| nfs-volume | 7.1.69 | 7.1.72 |
v40.16.0
Stemcell Updates
| Release | Old Version | New Version |
|---|---|---|
| ubuntu-jammy | 1.445 | 1.465 |
| stemcell-only |
v40.15.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 |
|---|---|---|---|
| credhub | 2.12.75 | 2.12.76 | |
| dotnet-core-buildpack | 2.4.28 | 2.4.29 | |
| nginx-buildpack | 1.2.14 | 1.2.15 | |
| nats | 56.19.0 | 56.20.0 | |
| python-buildpack | 1.8.25 | 1.8.26 | |
| pxc | 1.0.28 | 1.0.29 | |
| uaa | 77.9.0 | 77.10.0 | |
| backup-and-restore-sdk | 1.19.17 | 1.19.20 | |
| nfs-volume | 7.1.68 | 7.1.69 |
v40.14.0
Notices
🔒 Resolves CVE-2024-22279, which affected routing-releases 0.273.0 through 0.297.0 and cf-deployment 30.9.0 through 40.13.0.
Ops-files
Deleted Ops-files
The ops files for using the community postgres-boshrelease have been removed (#1182):
operations/community/use-community-postgres.ymloperations/community/use-community-postgres-ha.yml
To use an up-to-date version of Postgres, please use the ops file operations/use-postgres.yml.
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.147 | 42.0.148 | |
| diego | 2.99.0 | 2.100.0 | |
| java-buildpack | 4.69.0 | 4.70.0 | |
| routing | 0.297.0 | 0.298.0 | |
| postgres | 51 | 52 | |
| backup-and-restore-sdk | 1.19.16 | 1.19.17 | |
| winc | 2.24.0 | 2.25.0 |
v40.13.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 |
|---|---|---|---|
| binary-buildpack | 1.1.11 | 1.1.12 | |
| capi | 1.181.0 | 1.182.0 | |
| credhub | 2.12.74 | 2.12.75 | |
| cflinuxfs4 | 1.95.0 | 1.98.0 | |
| cf-smoke-tests | 42.0.146 | 42.0.147 | |
| dotnet-core-buildpack | 2.4.27 | 2.4.28 | |
| go-buildpack | 1.10.18 | 1.10.19 | |
| php-buildpack | 4.6.18 | 4.6.19 | |
| nodejs-buildpack | 1.8.24 | 1.8.25 | |
| r-buildpack | 1.2.11 | 1.2.12 | |
| nginx-buildpack | 1.2.13 | 1.2.14 | |
| python-buildpack | 1.8.23 | 1.8.25 | |
| ruby-buildpack | 1.10.13 | 1.10.15 | |
| staticfile-buildpack | 1.6.12 | 1.6.13 | |
| mapfs | 1.2.71 | 1.2.72 | |
| nfs-volume | 7.1.66 | 7.1.68 | |
| cflinuxfs4-compat | 1.95.0 | 1.98.0 |
v40.12.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 |
|---|---|---|---|
| capi | 1.180.0 | 1.181.0 | |
| credhub | 2.12.73 | 2.12.74 | |
| garden-runc | 1.52.0 | 1.53.0 | |
| java-buildpack | 4.68.0 | 4.69.0 | |
| routing | 0.296.0 | 0.297.0 | |
| mapfs | 1.2.70 | 1.2.71 | |
| nfs-volume | 7.1.65 | 7.1.66 | |
| smb-volume | 3.1.67 | 3.1.69 | |
| backup-and-restore-sdk | 1.19.14 | 1.19.16 | |
| windows2019 | 2019.72 | 2019.73 |
v40.11.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.18 | 1.2.19 | |
| cf-smoke-tests | 42.0.145 | 42.0.146 | |
| diego | 2.98.0 | 2.99.0 | |
| pxc | 1.0.27 | 1.0.28 | |
| uaa | 77.8.0 | 77.9.0 | |
| postgres | 49 | 51 | |
| haproxy | 13.5.0+2.8.9 | 14.0.0+2.8.9 | |
| mapfs | 1.2.69 | 1.2.70 | |
| nfs-volume | 7.1.64 | 7.1.65 |
v40.10.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.439 | 1.445 |
| stemcell-only |
v40.9.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.423 | 1.439 |
| stemcell-only |
v40.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 |
|---|---|---|---|
| cf-smoke-tests | 42.0.142 | 42.0.145 | |
| credhub | 2.12.72 | 2.12.73 | |
| loggregator-agent | 8.1.0 | 8.1.1 | |
| uaa | 77.5.0 | 77.8.0 | |
| windows2019 | 2019.71 | 2019.72 | |
| winc | 2.23.0 | 2.24.0 | |
| mapfs | 1.2.68 | 1.2.69 | |
| nfs-volume | 7.1.63 | 7.1.64 | |
| smb-volume | 3.1.66 | 3.1.67 | |
| backup-and-restore-sdk | 1.19.12 | 1.19.14 |