labels.facet_timestamp_1day=Within 24 hours
labels.facet_timestamp_1week=Within a week
labels.facet_timestamp_1month=Within a month
labels.facet_timestamp_1year=Within a year
labels.facet_timestamp_3month=Within 3 months
labels.facet_timestamp_6month=Within 6 months
labels.facet_timestamp_2year=Within 2 years
labels.facet_timestamp_3year=Within 3 years
labels.facet_contentLength_title=Size
labels.facet_contentLength_10k=  - 10KB

 * of the code may not be readable by older versions of the code (e.g., a serialized Bloom filter
 * generated today may <i>not</i> be readable by a binary that was compiled 6 months ago).
 *
 * <p>As of Guava 23.0, this class is thread-safe and lock-free. It internally uses atomics and
 * compare-and-swap to ensure correctness when multiple threads are used to access it.
 *

                    //highlight weekends
                    if (calendar[row][col].isoWeekday() > 5)
                        classes.push('weekend');

                    //grey out the dates in other months displayed at beginning and end of this calendar
                    if (calendar[row][col].month() != calendar[1][1].month())
                        classes.push('off', 'ends');

    public static final String LABELS_facet_timestamp_1year = "{labels.facet_timestamp_1year}";

    /** The key of the message: Within 3 months */
    public static final String LABELS_facet_timestamp_3month = "{labels.facet_timestamp_3month}";

    /** The key of the message: Within 6 months */
    public static final String LABELS_facet_timestamp_6month = "{labels.facet_timestamp_6month}";

- Extended the kube-apiserver loopback client certificate validity to 14 months to align with the updated Kubernetes support lifecycle. ([#130047](https://github.com/kubernetes/kubernetes/pull/130047), [@HirazawaUi](https://github.com/HirazawaUi)) [SIG API Machinery and Auth]

### Avoiding permanent beta

From Kubernetes 1.20 onwards, SIG Architecture will implement a new policy to transition all REST APIs out of beta within nine months. The idea behind the new policy is to avoid features staying in beta for a long time. Once a new API enters beta, it will have nine months to either:

 - reach GA, and deprecate the beta, or
 - have a new beta version _(and deprecate the previous beta)_.

* ⬆ Bump dawidd6/action-download-artifact from 3.0.0 to 3.1.4. PR [#11310](https://github.com/tiangolo/fastapi/pull/11310) by [@dependabot[bot]](https://github.com/apps/dependabot).
* ♻️ Refactor computing FastAPI People, include 3 months, 6 months, 1 year, based on comment date, not discussion date. PR [#11304](https://github.com/tiangolo/fastapi/pull/11304) by [@tiangolo](https://github.com/tiangolo).

*   `tf.lite`:
    *   The LiteRT [repo](https://github.com/google-ai-edge/LiteRT) is live (see [announcement](https://developers.googleblog.com/en/tensorflow-lite-is-now-litert/)), which means that in the coming months there will be changes to the development experience for TFLite. The TF Lite Runtime source will be moved later this year, and sometime after that we will start accepting contributions through that repo.