The detailed diff from the test failure should be included in the commit message, along with a reference
to the change that caused the failure. Updates to these files is exceptional, and requires extremely close review
to ensure we are not breaking backwards compatibility with serialized data from previous releases.

To see the diff between the original JSON/YAML data and the `...after_roundtrip...` files:

```sh

fi

# print a message based on the result
if [ $res -eq 0 ]; then
  echo 'Congratulations! All shell files are passing lint :-)'
else
  {
    echo
    echo 'Please review the above warnings. You can test via "./hack/verify-shellcheck.sh"'
    echo 'If the above warnings do not make sense, you can exempt this warning with a comment'
    echo ' (if your reviewer is okay with it).'

//  4. API server access **BEFORE** your hook has completed
//
// Think of it like a mini-controller that is super privileged and gets to run in-process
// If you use this feature, tag @deads2k on github who has promised to review code for anyone's PostStartHook
// until it becomes easier to use.
type PostStartHookFunc func(context PostStartHookContext) error

// PreShutdownHookFunc is a function that can be added to the shutdown logic.

* Pull Requests überprüfen (Review), [besonders wichtig für Übersetzungen](contributing.md#ubersetzungen){.internal-link target=_blank}.

Eine Runde Applaus für sie. 👏 🙇

## Aktivste Benutzer im letzten Monat

* [Créent des Pull Requests](help-fastapi.md#creer-une-pull-request){.internal-link target=_blank}.
* Review les Pull Requests, [particulièrement important pour les traductions](contributing.md#traductions){.internal-link target=_blank}.

Une salve d'applaudissements pour eux. 👏 🙇

## Utilisateurs les plus actifs le mois dernier

    - ncdc
    - tallclair
    - mwielgus
    - soltysh
    - jsafrane
    - dims
    - cici37
  # api-reviewers targeted by sig area
  # see https://git.k8s.io/community/sig-architecture/api-review-process.md#training-reviews
  sig-api-machinery-api-reviewers:
    - caesarxuchao
    - deads2k
    - jpbetz
    - sttts
    - cici37
  sig-apps-api-reviewers:
    - janetkuo
    - kow3ns
    - soltysh

  // Warnings over 256 characters and large numbers of warnings may be truncated.
  // +optional
  repeated string warnings = 7;
}

// AdmissionReview describes an admission review request/response.
message AdmissionReview {
  // Request describes the attributes for the admission request.
  // +optional
  optional AdmissionRequest request = 1;

  // Warnings over 256 characters and large numbers of warnings may be truncated.
  // +optional
  repeated string warnings = 7;
}

// AdmissionReview describes an admission review request/response.
message AdmissionReview {
  // Request describes the attributes for the admission request.
  // +optional
  optional AdmissionRequest request = 1;

        Prefer to use the `Annotated` version if possible.

    ```Python hl_lines="2  5  9  13  47  65  106  108-116  122-125  129-135  140  156"
    {!> ../../../docs_src/security/tutorial005.py!}
    ```

Now let's review those changes step by step.

## OAuth2 Security scheme

The first change is that now we are declaring the OAuth2 security scheme with two available scopes, `me` and `items`.

image::ci-systems/teamcity-step-upd.png[]

TeamCity will start the build and you’ll be able to view the build progress
by clicking _Build Configuration Home_.
When the build is finished, you can review the build results by clicking the build number link:

image::ci-systems/teamcity-results.png[]

You can view the tests right here in TeamCity:

image::ci-systems/teamcity-tests.png[]