### (No, really, you MUST read this before you upgrade)

- The StreamingProxyRedirects feature and `--redirect-container-streaming` flag are deprecated, and will be removed in a future release. The default behavior (proxy streaming requests through the kubelet) will be the only supported option.

*   `tf.keras`:
    *   `OMP_NUM_THREADS` is no longer used by the default Keras config. To
        configure the number of threads, use `tf.config.threading` APIs.
    *   `tf.keras.model.save_model` and `model.save` now defaults to saving a
        TensorFlow SavedModel.
    *   `keras.backend.resize_images` (and consequently,

16FE5..16FEF  ; disallowed                             # NA   <reserved-16FE5>..<reserved-16FEF>
16FF0..16FF1  ; valid                                  # 13.0 VIETNAMESE ALTERNATE READING MARK CA..VIETNAMESE ALTERNATE READING MARK NHAY
16FF2..16FFF  ; disallowed                             # NA   <reserved-16FF2>..<reserved-16FFF>

For example, if you had a database session in a dependency with `yield`, the `StreamingResponse` would not be able to use that session while streaming data because the session would have already been closed in the exit code after `yield`.

This behavior was reverted in 0.118.0, to make the exit code after `yield` be executed after the response is sent.

error if FIPS 140-3 mode can't be enabled. func Supported() error { // Keep this in sync with fipsSupported in cmd/dist/test.go. // ASAN disapproves of reading swaths of global memory in fips140/check. // One option would be to expose runtime.asanunpoison through // crypto/internal/fips140deps and then call it to unpoison the range // before reading it, but it is unclear whether that would then cause // false negatives. For now, FIPS+ASAN doesn't need to work. if asanEnabled { return errors.New("FIPS...

// validation still applies. if puregoEnabled { return errors.New("FIPS 140-3 mode is incompatible with the purego build tag") } // ASAN disapproves of reading swaths of global memory in fips140/check. // One option would be to expose runtime.asanunpoison through // crypto/internal/fips140deps and then call it to unpoison the range // before reading it, but it is unclear whether that would then cause // false negatives. For now, FIPS+ASAN doesn't need to work. if asanEnabled { return errors.New("FIPS...