*  In the `keras` PyPI package, accessible symbols are now restricted to symbols that are intended to be public. This may affect your code if you were using `import keras` and you used `keras` functions that were not public APIs, but were accessible in earlier versions with direct imports. In those cases, please use the following guideline:

- Fixed a bug that the kubelet cannot start on BtrfS. ([#98015](https://github.com/kubernetes/kubernetes/pull/98015), [@gjkim42](https://github.com/gjkim42)) [SIG Node]
- Fixed a bug where aggregator_unavailable_apiservice metrics were reported for deleted apiservices. ([#96421](https://github.com/kubernetes/kubernetes/pull/96421), [@dgrisonnet](https://github.com/dgrisonnet)) [SIG API Machinery and Instrumentation]

!purego #include "textflag.h" // This is a port of the s390x asm implementation. // to ppc64le. // Some changes were needed due to differences in // the Go opcodes and/or available instructions // between s390x and ppc64le. // 1. There were operand order differences in the // VSUBUQM, VSUBCUQ, and VSEL instructions. // 2. ppc64 does not have a multiply high and low // like s390x, so those were implemented using // macros to compute the equivalent values. // 3. The LVX, STVX instructions on ppc64 require...

!purego #include "textflag.h" // This is a port of the s390x asm implementation. // to ppc64le. // Some changes were needed due to differences in // the Go opcodes and/or available instructions // between s390x and ppc64le. // 1. There were operand order differences in the // VSUBUQM, VSUBCUQ, and VSEL instructions. // 2. ppc64 does not have a multiply high and low // like s390x, so those were implemented using // macros to compute the equivalent values. // 3. The LVX, STVX instructions on ppc64 require...

Discussed here: [#11522](https://github.com/fastapi/fastapi/pull/11522) and here: [#11525](https://github.com/fastapi/fastapi/discussions/11525)

### Docs

.carousel.pointer-event should ideally be pan-y (to allow for users to scroll vertically)\n//    even when their scroll action started on a carousel, but for compatibility (with Firefox)\n//    we're preventing all actions instead\n// 2. The .carousel-item-left and .carousel-item-right is used to indicate where\n//    the active slide is heading.\n// 3. .active.carousel-item is the current slide.\n// 4. .active.carousel-item-left and .active.carousel-item-right is the current\n//    slide in its in-transition...

.carousel.pointer-event should ideally be pan-y (to allow for users to scroll vertically)\n//    even when their scroll action started on a carousel, but for compatibility (with Firefox)\n//    we're preventing all actions instead\n// 2. The .carousel-item-start and .carousel-item-end is used to indicate where\n//    the active slide is heading.\n// 3. .active.carousel-item is the current slide.\n// 4. .active.carousel-item-start and .active.carousel-item-end is the current\n//    slide in its in-transition...