# Howto: Submit patches for 5.4.1

**URL:** <https://discourse.itk.org/t/howto-submit-patches-for-5-4-1/6651>\
**Category:** Engineering\
**Tags:** itk\
**Created:** [May 21, 2024, 10:37am UTC](https://discourse.itk.org/t/howto-submit-patches-for-5-4-1/6651 "2024-05-21T10:37:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![phcerdan](https://discourse.itk.org/user_avatar/discourse.itk.org/phcerdan/32/286_2.png) [@phcerdan](https://discourse.itk.org/u/phcerdan)\
**Post date:** [May 21, 2024, 10:37am UTC](https://discourse.itk.org/t/howto-submit-patches-for-5-4-1/6651/1 "2024-05-21T10:37:42Z")

</div>

ITK v5.4.0 has been [tagged](https://github.com/InsightSoftwareConsortium/ITK/tree/v5.4.0)! 🏷

We have a new [`release-5.4`](https://github.com/InsightSoftwareConsortium/ITK/tree/release-5.4) branch. 🚀  
Patches intended for future 5.4 patch releases (`5.4.1`, etc) should be branched from here and a pull-request created against this branch:

**Branch from `release-5.4`:**

```bash
git checkout release-5.4
git checkout -b new_patch_for_5.4
# hack hack
git commit -m 'COMP: Fix warning for ...'
git push phcerdan

```

**Open PR against the upstream release-5.4 branch**  
Once the commit is in your fork of ITK, open a pull-request and manually choose the `release-5.4` branch.

 ![image](https://discourse.itk.org/uploads/default/original/2X/b/bc45c9129fbd3f44646e65e3b1ad464ebaf61e6d.png)

The actual release of `5.4.0` will be announced shortly 🕐