Answers.Body: <p>After reding through this <a href="https://nystudio107.com/blog/updating-craft-cms-without-headaches" rel="nofollow noreferrer">https://nystudio107.com/blog/updating-craft-cms-without-headaches</a> I nuked the vendor folder and reset everything using this command</p>
  <pre><code>rm -rf vendor/ &amp;&amp; rm composer.lock &amp;&amp; composer clear-cache &amp;&amp; composer update
  </code></pre>
  <p>This sorted my issue and I am now fully up to date and will only do future updates via commandline</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-05-27T09:11:55.290Z
Answers.LastActivityDate: 2024-05-27T09:11:55.290Z
Answers.UserDisplayName: bhackett
Answers.Body: <p>You likely have pinned versions set for those four plugins. Check your <code>composer.json</code> file; do those plugins have a <code>^</code> before the versions or not? If not, they're pinned to those versions and will not update to the next non-major version.</p>
  <p>Why?</p>
  <p>Because updating Craft and plugins via the Craft control panel results in Craft pinning the versions of whatever it installs or updates. Through the command line that does not happen.</p>
  <p>Since you describe doing updates both through the command line and the Craft control panel, you're getting a mix of both, and that can have (un)predictable results. You should choose one method (command line or control panel) and stick with it and always do it that way.</p>
  <p>To fix your issue: add <code>^</code> to the versions of the packages in your <code>composer.json</code> where they aren't and then update again from the command line. Everything should update as expected.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-05-21T15:55:15.570Z
Answers.Text: Thanks for the answer and that all makes sense, but the solution doesn't work for me . I have added the caret `^` to the plugins in composer. Json and ran the update in command line but the same thing happens with the updates completing but not updating. When in look at composer. json after the update the ^ I added has been stripped out and the version is set to the latest version of the plugin. I have also tried setting the plugin version back to be the same as the version that I have installed but again the ^ gets stripped out and version changed to the latest. Thaks for any help
Answers.UserDisplayName: bhackett
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-05-06T15:28:38.550Z
Answers.LastActivityDate: 2024-05-06T15:28:38.550Z
Answers.UserDisplayName: CraftQuest
Body: <p>In Craft CMS 4.8.10 I have updated my plugins via command-line and in the control panel and they both come back with the updates successful. But in the control panel the updates continue to appear again and if I run the update in command line the same thing happens with those updates listed again as needed to be installed.</p>
  <p>Strange this is it is a set of updates for 4 plugins Ckeditor, Seomatic, Supertable and Imager x. Updates for some other plugins and craft itself have come in since this issue arose and when I run the update they complete and don't show again but those other plugins stuck.
  Thanks for any help</p>
  
Tags: <plugins><updates><updating>
Title: Updated plugins keep showing in the control panel and command line
ThreadText: # Updated plugins keep showing in the control panel and command line
  
  (Asked by: username_0 on 2024-04-29)
  
  In Craft CMS 4.8.10 I have updated my plugins via command-line and in the control panel and they both come back with the updates successful. But in the control panel the updates continue to appear again and if I run the update in command line the same thing happens with those updates listed again as needed to be installed.
  
  Strange this is it is a set of updates for 4 plugins Ckeditor, Seomatic, Supertable and Imager x. Updates for some other plugins and craft itself have come in since this issue arose and when I run the update they complete and don't show again but those other plugins stuck.
  Thanks for any help
  
  **Tags:** plugins, updates, updating
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2024-05-27. Score: 1 | Accepted answer
  
  After reding through this <https://nystudio107.com/blog/updating-craft-cms-without-headaches> I nuked the vendor folder and reset everything using this command
  
  ```
  rm -rf vendor/ && rm composer.lock && composer clear-cache && composer update
  
  ```
  
  This sorted my issue and I am now fully up to date and will only do future updates via commandline
  
  
  ---
  
  ### Answer by username_1 on 2024-05-06. Score: 2
  
  You likely have pinned versions set for those four plugins. Check your `composer.json` file; do those plugins have a `^` before the versions or not? If not, they're pinned to those versions and will not update to the next non-major version.
  
  Why?
  
  Because updating Craft and plugins via the Craft control panel results in Craft pinning the versions of whatever it installs or updates. Through the command line that does not happen.
  
  Since you describe doing updates both through the command line and the Craft control panel, you're getting a mix of both, and that can have (un)predictable results. You should choose one method (command line or control panel) and stick with it and always do it that way.
  
  To fix your issue: add `^` to the versions of the packages in your `composer.json` where they aren't and then update again from the command line. Everything should update as expected.
  
  > **Comments:**
  > **username_0**: Thanks for the answer and that all makes sense, but the solution doesn't work for me . I have added the caret `^` to the plugins in composer. Json and ran the update in command line but the same thing happens with the updates completing but not updating. When in look at composer. json after the update the ^ I added has been stripped out and the version is set to the latest version of the plugin. I have also tried setting the plugin version back to be the same as the version that I have installed but again the ^ gets stripped out and version changed to the latest. Thaks for any help  
  
  ---
  
  