Releases: cloudfoundry/stembuild
Releases · cloudfoundry/stembuild
2019.17
Release Notes:
- Supports signed URL capability. If Windows users opt in, the bosh agent will manage artifacts on the blobstore using signed URLs rather than blobstore credentials. See bosh documentation for more information on how to opt into signed URLs.
- Stembuild checks whether the OS version of the VM is Windows Server 2019, OS build 17763. This is the only OS version that any stembuild v2019.x is compatible with.
- Fixed a bug that required access to the public Windows Update Server to get updated root certificates for stembuild construct to execute successfully.
- Note: if your VM does not have access to the public Windows Update Server, you will need to keep your certificates updated manually.
- Fixed a bug that tried to validate your VM credentials before connecting to the VM via WinRM. The workaround detailed in this KB should no longer be necessary for 2019.17.
2019.15
Release Notes:
- Includes Microsoft Security Updates Patch Tuesday January 14th, 2020
- This includes fixes for CVE-2020-0601.
- Root certificates on machines deployed using stembuild-built stemcells get updated
- Note: this requires internet connection to the Windows Updates Server to update successfully.
2019.14
Release Notes:
- Includes Microsoft Security Updates Patch Tuesday December 10th, 2019
- Updated stembuild to always use the latest version of OpenSSH (v8.0.0-p1-beta as of this release)
- Root certificates on machines deployed using stembuild-built stemcells get updated certificates from the Windows Updates Server
2019.13
Release Notes:
- Includes Microsoft Security Updates Patch Tuesday November 12th, 2019
- Added logging and exit code to
stembuild construct
to allow users to see the progress of the command and know whether it has completed preparing the VM for packaging - Added retry behavior for the file rename operation in the compilation VM to reduce risk of compilation failure due to custom antivirus installations in the base image
1803.17
Note: Windows Server v1803 is out of mainstream support. This is the last release of stembuild specific to Windows Server v1803.
Release Notes:
- Includes Microsoft Security Updates Patch Tuesday November 12th, 2019
- Added retry behavior for the file rename operation in the compilation VM to reduce risk of compilation failure due to custom antivirus installations in the base image
2019.12
- Includes Microsoft Security Updates Patch Tuesday October 8th, 2019
- Added a flag to
stembuild package
to allow user to specify patch version for the stemcell .tgz output - Fixed a bug where
stembuild construct
was failing to execute with a DISM error - Aligned Internet Explorer-based policies in stemcells built using stembuild with Microsoft Baseline Security Standard
1803.16
- Includes Microsoft Security Updates Patch Tuesday October 8th, 2019
- Added a flag to
stembuild package
to allow user to specify patch version for the stemcell .tgz output
2019.11
- Includes Microsoft Security Updates Patch Tuesday September 10th, 2019
- Enabled the Hyper-V Windows feature for Windows 2019 stemcells built using Stembuild
- Fixed a bug that left user directories on the target machines after a user had terminated a BOSH ssh connection into that machine
- Deleted:
.ssh
directory and all normal files in the home directory that may have been created during the ssh session - Not Deleted:
.dat
files loaded as part of the registry hive when a user logs in. Files will exist with file locks until the next VM reboot.
- Deleted:
1803.15
- Includes Microsoft Security Updates Patch Tuesday September 2019
- Fixed a bug that left user directories on the target machines after a user had terminated a BOSH ssh connection into that machine
- Deleted:
.ssh
directory and all normal files in the home directory that may have been created during the ssh session - Not Deleted:
.dat
files loaded as part of the registry hive when a user logs in. Files will exist with file locks until the next VM reboot.
- Deleted:
1803.14
Update README.md