finally:
        some_cleanup()
```

...that way the `finally` block is run regardless of any exception that might happen.

### Features

* The same PR [#4575](https://github.com/tiangolo/fastapi/pull/4575) from above also fixes the `contextvars` context for the code before and after `yield`. This was the main objective of that PR.

/**
 * Fess RAG Chat JavaScript
 * Enhanced with Atlassian Design System patterns
 */
var FessChat = (function() {
    'use strict';

    var config = {
        apiUrl: '/api/v1/chat',
        streamUrl: '/api/v1/chat/stream',
        labels: {
            thinking: 'Thinking...',
            waiting: '...',
            error: 'An error occurred. Please try again.',
            sources: 'Sources',
            statusReady: 'AI Assistant',

/* ============================================
   Chat messages area
   ============================================ */
.chat-messages {
    flex: 1;
    overflow-y: auto;
    padding: 1rem;
    scroll-behavior: smooth;
    min-height: 200px;
}

.chat-messages:not(:has(.chat-message)) .empty-state {
    display: flex;
}

.chat-messages:has(.chat-message) .empty-state {
    display: none;
}

pkg syscall (netbsd-arm64-cgo), type IfAnnounceMsghdr struct, Type uint8
pkg syscall (netbsd-arm64-cgo), type IfAnnounceMsghdr struct, Version uint8
pkg syscall (netbsd-arm64-cgo), type IfAnnounceMsghdr struct, What uint16
pkg syscall (netbsd-arm64-cgo), type IfData struct
pkg syscall (netbsd-arm64-cgo), type IfData struct, Addrlen uint8
pkg syscall (netbsd-arm64-cgo), type IfData struct, Baudrate uint64

The behavior of some watch calls to the server when filtering on fields was incorrect. If watching objects with a filter, when an update was made that no longer matched the filter a DELETE event was correctly sent. However, the object that was returned by that delete was not the (correct) version before the update, but instead, the newer version. That meant the new object was not matched by the filter. This was a regression from behavior between cached watches on the server side and uncached watches,...

This release contains changes that address the following vulnerabilities:

### CVE-2021-25735: Validating Admission Webhook does not observe some previous fields

A security issue was discovered in kube-apiserver that could allow node
updates to bypass a Validating Admission Webhook. You are only affected
by this vulnerability if you run a Validating Admission Webhook for Nodes

pkg syscall (freebsd-arm64), type IfAnnounceMsghdr struct, Type uint8
pkg syscall (freebsd-arm64), type IfAnnounceMsghdr struct, Version uint8
pkg syscall (freebsd-arm64), type IfAnnounceMsghdr struct, What uint16
pkg syscall (freebsd-arm64), type IfData struct
pkg syscall (freebsd-arm64), type IfData struct, Addrlen uint8
pkg syscall (freebsd-arm64), type IfData struct, Baudrate uint64

This release contains changes that address the following vulnerabilities:

### CVE-2021-25735: Validating Admission Webhook does not observe some previous fields

A security issue was discovered in kube-apiserver that could allow node
updates to bypass a Validating Admission Webhook. You are only affected
by this vulnerability if you run a Validating Admission Webhook for Nodes

- Fixed an issue in the kubelet that showed when writeable layers and read-only layers were at different paths within the same mount.
  Kubernetes was previously detecting that the image filesystem was split, even when that was not really the case ([#128344](https://github.com/kubernetes/kubernetes/pull/128344), [@kannon92](https://github.com/kannon92)) [SIG Node]

then the <code>File</code> interface is implemented by both <code>S1</code> and
<code>S2</code>, regardless of what other methods
<code>S1</code> and <code>S2</code> may have or share.
</p>

<p>
Every type that is a member of the type set of an interface implements that interface.
Any given type may implement several distinct interfaces.