Skip to content

Releases: cloudfoundry/diego-release

Diego v2.65.0

26 Jul 19:37
Compare
Choose a tag to compare

Changes

  • Replace GinkgoParallelNode with GinkgoParallelProcess @ebroberson (#630)
  • Bump Golang to go1.18.4 @cf-diego (#625)
    Breaking Changes: The diego components are now more strict about the protocols used in TLS communications, causing integrations with systems using older, insecure protocols to fail. These components have been updated to Go 1.18, and will no longer support TLS 1.0 and 1.1 connections or certificates with a SHA-1 checksum. This is most likely to affect connections with external databases.

Resources

✨ Built with go 1.18.4

Diego v2.64.0

18 May 23:14
Compare
Choose a tag to compare

Diego v2.63.0

15 Apr 23:55
Compare
Choose a tag to compare

Changes

  • Pass log config in container spec to garden, so that vxlan-policy-agent can send app logs

Resources

Diego v2.62.0

01 Apr 16:47
Compare
Choose a tag to compare

Diego v2.61.0

04 Mar 20:01
Compare
Choose a tag to compare

NOTE on release version

Diego release v2.60.0 does not exist; never had, never will. One of our engineers accidentally pressed a button in our CI to bump the version number independent of actually releasing anything. 🙃 Sorry! 🙇

Resources

Changes

✨ Built with golang 1.17.8

v2.59.0

23 Feb 20:49
Compare
Choose a tag to compare

Resources

Changes

  • Deprecate start and evacuate_running endpoints @moleske (#617)
  • Ensure containers can eventually communicate over TLS using application internal route even if synchronous communication fails.
    • ⚠️ This introduces a new migration to the BBS for the first time in nearly 4 years. Once you deploy this version you can not easily rollback.

✨ Built with golang 1.17.5

v2.58.1

17 Feb 18:40
Compare
Choose a tag to compare

SAME AS v2.59.0

v2.58.0

31 Jan 16:52
Compare
Choose a tag to compare

Resources

Changes

✨ Built with golang 1.17.5

v2.57.0

10 Jan 16:06
Compare
Choose a tag to compare

Resources

Changes

✨ Built with golang 1.17.5

v2.56.0

23 Dec 00:07
Compare
Choose a tag to compare

Resources

Changes

  • C2C certificate is regenerated when internal routes are updated (#588)