From Cloud.gov:
"cloud.gov frequently updates the programming language buildpacks available to
our customers. Buildpack updates include programming language updates and
often include security fixes.
We recently updated buildpacks in use by your applications. You should
restage or redeploy your applications to take advantage of the update.
A rolling restage operation is the quickest way to upgrade without incurring
downtime. You may still want to leverage your deployment infrastructure to
perform the upgrade if you have compliance requirements for redeployment operations.
You can restage your applications by opening the command line and entering
the following commands:
cf target -o gsa-smartpay -s dev ; cf restage --strategy rolling smartpay-training
From Mark Meyer: "This is something we need to do periodically. It's basically an update to the software running the sites. KL&A will be able to do this and should get these notifications once we can add them to the cloud.gov account. It doesn't take much time once you have access to the account."
From Cloud.gov: "cloud.gov frequently updates the programming language buildpacks available to our customers. Buildpack updates include programming language updates and often include security fixes.
We recently updated buildpacks in use by your applications. You should restage or redeploy your applications to take advantage of the update.
A rolling restage operation is the quickest way to upgrade without incurring downtime. You may still want to leverage your deployment infrastructure to perform the upgrade if you have compliance requirements for redeployment operations.
You can restage your applications by opening the command line and entering the following commands:
cf target -o gsa-smartpay -s dev ; cf restage --strategy rolling smartpay-training
cf target -o gsa-smartpay -s prod ; cf restage --strategy rolling smartpay-training
cf target -o gsa-smartpay -s staging ; cf restage --strategy rolling smartpay-training
cf target -o gsa-smartpay -s prod ; cf restage --strategy rolling smartpay-889
cf target -o gsa-smartpay -s dev ; cf restage --strategy rolling smartpay-889
cf target -o gsa-smartpay -s staging ; cf restage --strategy rolling smartpay-889
For more information about the buildpack update(s), please see the following release notes:
go_buildpack v1.10.13: https://github.com/cloudfoundry/go-buildpack/releases/tag/v1.10.13
nodejs_buildpack v1.8.18: https://github.com/cloudfoundry/nodejs-buildpack/releases/tag/v1.8.18
python_buildpack v1.8.15: https://github.com/cloudfoundry/python-buildpack/releases/tag/v1.8.15
ruby_buildpack v1.10.5: https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.10.5
php_buildpack v4.6.11: https://github.com/cloudfoundry/php-buildpack/releases/tag/v4.6.11
dotnet_core_buildpack v2.4.17: https://github.com/cloudfoundry/dotnet-core-buildpack/releases/tag/v2.4.17
For more information on keeping your application updated and secure, see: https://cloud.gov/docs/getting-started/app-maintenance/
If you have questions, you can email us at cloud-gov-support@gsa.gov."
From Mark Meyer: "This is something we need to do periodically. It's basically an update to the software running the sites. KL&A will be able to do this and should get these notifications once we can add them to the cloud.gov account. It doesn't take much time once you have access to the account."