# CLI update command prompts for version 4.3.0-Beta, despite update\_stability being set to 'stable'

**URL:** <https://forum.mautic.org/t/cli-update-command-prompts-for-version-4-3-0-beta-despite-update-stability-being-set-to-stable/24148>\
**Category:** Product Support\
**Tags:** mautic-4\
**Created:** [May 18, 2022, 6:31pm UTC](https://forum.mautic.org/t/cli-update-command-prompts-for-version-4-3-0-beta-despite-update-stability-being-set-to-stable/24148 "2022-05-18T18:31:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![steverobinson](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/steverobinson/32/174_2.png) [@steverobinson](https://forum.mautic.org/u/steverobinson)\
**Post date:** [May 18, 2022, 6:31pm UTC](https://forum.mautic.org/t/cli-update-command-prompts-for-version-4-3-0-beta-despite-update-stability-being-set-to-stable/24148/1 "2022-05-18T18:31:28Z")

</div>

**Your software**  
My Mautic version is: 4.2.2.  
My PHP version is: 7.4  
My Database type and version is: MariaDB 10

**Your problem**  
My problem is:  
When running the CLI command mautic:update:find in my production environment, I am prompted to upgrade to 4.3.0-Beta, despite the local.php config setting of update\_stability being correctly set to ‘stable’

```auto
Version 4.3.0-beta of Mautic is available for download. Please visit https://github.com/mautic/mautic/releases/tag/4.3.0-beta for more information.
To update, you can run 'php bin/console mautic:update:apply' from the command line.

```

Steps I have tried to fix the problem:  
Verified the update\_stability setting on the box I am updating and confirmed behavior is consistent across other production boxes.

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [May 18, 2022, 9:14pm UTC](https://forum.mautic.org/t/cli-update-command-prompts-for-version-4-3-0-beta-despite-update-stability-being-set-to-stable/24148/2 "2022-05-18T21:14:33Z")

</div>

Thanks Steve, per conversations on Slack we identified that there was a mistake made in the release process, and the stability channel was set incorrectly to Stable.

I’ve deleted the release to prevent accidental updates and we will re-release tomorrow.