Releases: cloudfoundry/cf-deployment
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 |
v39.2.0
Stemcell Updates
| Release | Old Version | New Version |
|---|---|---|
| ubuntu-jammy | 1.379 | 1.390 |
| stemcell-only |
v39.1.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.93.0 | 2.94.0 | |
| credhub | 2.12.62 | 2.12.63 | |
| cflinuxfs4 | 1.72.0 | 1.75.0 | |
| garden-runc | 1.49.0 | 1.50.0 | |
| routing | 0.291.0 | 0.292.0 | |
| python-buildpack | 1.8.19 | 1.8.20 | |
| uaa | 77.0.0 | 77.1.0 | |
| smb-volume | 3.1.55 | 3.1.56 | |
| cflinuxfs4-compat | 1.72.0 | 1.74.0 | |
| hwc-buildpack | 3.1.34 | 3.1.35 | |
| mapfs | 1.2.57 | 1.2.58 | |
| nfs-volume | 7.1.53 | 7.1.54 | |
| backup-and-restore-sdk | 1.19.1 | 1.19.2 |
v39.0.0
Notices
The absolute_entitlement and absolute_usage metrics have been replaced with the cpu_entitlement metric in the diego/bbs job. It no longer emits the absolute cpu entitlement metrics by default. Please update dashboards to use the new metric. Additionally, the experimental CPU Entitlement Plug-in no longer works.
For details, see PR #1164.
Ops-files
New Ops-files
Restore the previous metrics with these ops files:
https://github.com/cloudfoundry/cf-deployment/blob/develop/operations/use-absolute-cpu-entitlement-persistent-isolation-segment.yml
https://github.com/cloudfoundry/cf-deployment/blob/develop/operations/use-absolute-cpu-entitlement-windows2019.yml
https://github.com/cloudfoundry/cf-deployment/blob/develop/operations/use-absolute-cpu-entitlement.yml
Updated Ops-files
Similar to the cf-deployment.yml template, the bbs job in these ops files no longer emits absolute cpu entitlement metrics:
https://github.com/cloudfoundry/cf-deployment/blob/main/operations/add-persistent-isolation-segment-diego-cell.yml
https://github.com/cloudfoundry/cf-deployment/blob/develop/operations/windows2019-cell.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-networking | 3.42.0 | 3.43.0 | |
| capi | 1.172.0 | 1.173.0 | |
| credhub | 2.12.61 | 2.12.62 | |
| dotnet-core-buildpack | 2.4.23 | 2.4.24 | |
| php-buildpack | 4.6.14 | 4.6.15 | |
| silk | 3.42.0 | 3.43.0 | |
| backup-and-restore-sdk | 1.19.0 | 1.19.1 | |
| winc | 2.20.0 | 2.21.0 |
v38.1.0
Notices
- In certain situations the
/v3/service_plansendpoint returns duplicate entries. This is caused by an error in the database query fetching service plans based on their visibility in organizations accessible by the user issuing the request. These duplicates may result in failing service-related commands, e.g.cf create-servicefailing withService offering '...' is provided by multiple service brokers. - This has been fixed in CAPI 1.173.0.
Stemcell Updates
| Release | Old Version | New Version |
|---|---|---|
| ubuntu-jammy | 1.360 | 1.379 |
| stemcell-only |
v38.0.0
Notices
- Remove UAA's ability to act as a SAML identity provider
- Remove deprecated native MFA feature
See also https://github.com/cloudfoundry/uaa/releases/tag/v77.0.0 for more information.
- In certain situations the
/v3/service_plansendpoint returns duplicate entries. This is caused by an error in the database query fetching service plans based on their visibility in organizations accessible by the user issuing the request. These duplicates may result in failing service-related commands, e.g.cf create-servicefailing withService offering '...' is provided by multiple service brokers. - This has been fixed in CAPI 1.173.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 |
|---|---|---|---|
| cflinuxfs4 | 1.71.0 | 1.72.0 | |
| cf-smoke-tests | 42.0.130 | 42.0.133 | |
| cf-networking | 3.41.0 | 3.42.0 | |
| capi | 1.171.0 | 1.172.0 | |
| go-buildpack | 1.10.15 | 1.10.16 | |
| garden-runc | 1.48.0 | 1.49.0 | |
| dotnet-core-buildpack | 2.4.22 | 2.4.23 | |
| diego | 2.92.0 | 2.93.0 | |
| nginx-buildpack | 1.2.10 | 1.2.11 | |
| nodejs-buildpack | 1.8.21 | 1.8.22 | |
| staticfile-buildpack | 1.6.9 | 1.6.10 | |
| silk | 3.41.0 | 3.42.0 | |
| ruby-buildpack | 1.10.8 | 1.10.9 | |
| routing | 0.290.0 | 0.291.0 | |
| uaa | 76.31.0 | 77.0.0 | |
| windows2019fs | 2.62.0 | 2.63.0 | |
| windowsfs | 2.62.0 | 2.63.0 | |
| windows2019 | 2019.69 | 2019.70 | |
| cflinuxfs4-compat | 1.70.0 | 1.72.0 | |
| envoy-nginx | 0.23.0 | 0.24.0 | |
| backup-and-restore-sdk | 1.18.119 | 1.19.0 | |
| mapfs | 1.2.56 | 1.2.57 | |
| nfs-volume | 7.1.52 | 7.1.53 | |
| smb-volume | 3.1.53 | 3.1.55 |
v37.5.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 |
|---|---|---|---|
| bpm | 1.2.14 | 1.2.16 | |
| credhub | 2.12.60 | 2.12.61 | |
| cflinuxfs4 | 1.68.0 | 1.71.0 | |
| cf-smoke-tests | 42.0.128 | 42.0.130 | |
| dotnet-core-buildpack | 2.4.21 | 2.4.22 | |
| pxc | 1.0.23 | 1.0.24 | |
| routing | 0.289.0 | 0.290.0 | |
| cflinuxfs4-compat | 1.68.0 | 1.70.0 | |
| mapfs | 1.2.55 | 1.2.56 | |
| nfs-volume | 7.1.47 | 7.1.52 | |
| postgres | 48 | 49 |