Skip to content

v77.0.0 - UAA Release v77.0.0

Choose a tag to compare

@cf-identity cf-identity released this 14 Feb 12:35
· 1169 commits to develop since this release

What's Changed

New UAA

⚠️ Breaking Changes

Dependency Bumps

  • Bump github.com/cloudfoundry/bosh-utils from 0.0.425 to 0.0.426 in /src/acceptance_tests by @dependabot in #757
  • Bump github.com/onsi/gomega from 1.31.0 to 1.31.1 in /src/acceptance_tests by @dependabot in #756
  • Ignore gomega bump in uaa v74.5.x branch. by @hsinn0 in #764
  • Bump github.com/cloudfoundry/bosh-utils from 0.0.426 to 0.0.427 in /src/acceptance_tests by @dependabot in #766
  • Bump diff-lcs from 1.5.0 to 1.5.1 by @dependabot in #767
  • Bump github.com/cloudfoundry/bosh-utils from 0.0.427 to 0.0.428 in /src/acceptance_tests by @dependabot in #773
  • Bump nokogiri from 1.16.0 to 1.16.2 by @dependabot in #778
  • Bump rspec from 3.12.0 to 3.13.0 by @dependabot in #777
  • Bump minitest from 5.21.2 to 5.22.0 by @dependabot in #783
  • Bump github.com/cloudfoundry/bosh-utils from 0.0.428 to 0.0.430 in /src/acceptance_tests by @dependabot in #785
  • Bump minitest from 5.22.0 to 5.22.1 by @dependabot in #786
  • Revert "Bump github.com/cloudfoundry/bosh-utils in /src/acceptance tests (#785)" by @swalchemist in #787

Misc

Known Issues

  • During the upgrade to this version from UAA v76 or below with canary deployment (where briefly both new and old UAA servers could be running), UAA delete user endpoint might respond with an error even though the user deletion is successful. Mitigation: Delete users after the canary deployment finishes. But if you do run into this issue, you can ignore the error and check whether the user has been successfully deleted after the canary deployment finishes.

Full Changelog: v76.31.0...v77.0.0