Answers.Body: <p>The reason the Plugin Store hasn't picked up the 2.0.1 release is that you've got 3 different 2.0.1 tags in the repo.</p>
  
  <p><a href="https://i.sstatic.net/kXtZr.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/kXtZr.jpg" alt="enter image description here"></a></p>
  
  <p>Usually, that's not a problem as it will just pick the first one by date.</p>
  
  <p>In this case, if you browse the first "V2.0.1" tag, you'll see that its composer.json file has a listed version of 2.0.0, which is a version mismatch, so the Plugin Store will ignore it. <a href="https://github.com/hillholliday/Craft-User-Manual/blob/00e2808e328e5bfe793fd343a59b5d2445d84d27/composer.json#L5" rel="nofollow noreferrer">https://github.com/hillholliday/Craft-User-Manual/blob/00e2808e328e5bfe793fd343a59b5d2445d84d27/composer.json#L5</a></p>
  
  <p>The reasons 2.0.2 never got picked up is because there is no 2.0.2 tag in the repo.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-04T18:05:34.017Z
Answers.Text: Thanks Brad, that makes perfect sense. I didn't realize the plugin store looked at git tags. I'll update accordingly.
Answers.UserDisplayName: Rob Erskine
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-01T00:35:18.627Z
Answers.LastActivityDate: 2019-03-01T00:35:18.627Z
Answers.UserDisplayName: Brad Bell
Body: <p>I have a <a href="https://github.com/hillholliday/Craft-User-Manual/" rel="nofollow noreferrer">custom plugin</a> registered with <a href="https://id.craftcms.com/" rel="nofollow noreferrer">id.craftcms.com</a>. </p>
  
  <p><img src="https://cl.ly/368a5bd83718/Screen%20Shot%202019-02-28%20at%2010.46.10%20AM.jpg" alt="id.craft.cms changelog screenshot"></p>
  
  <p>The plugin store currently sees it at as 2.0.0, but I have since updated the plugin to 2.0.1 (and subsequently tried to force a silent 2.0.2 update) and noted so in my <a href="https://github.com/hillholliday/Craft-User-Manual/blob/master/CHANGELOG.md" rel="nofollow noreferrer">changelog</a> but the plugin store is not seeing this update.</p>
  
  <p>The contents of my changelog look like this:</p>
  
  <pre><code># Release Notes for Craft User Manual
  
  ## 2.0.2 - 2019-02-27
  ### Updated
  - Forcing new version for deprecation issues
  
  ## 2.0.1 - 2018-08-24
  ### Fixed
  - Deprecation Issues
  
  ## 2.0.0 - 2018-08-24
  ### Added
   - Initial Craft 3 release
  </code></pre>
  
  <p>This was lifted directly from <a href="https://docs.craftcms.com/v3/extend/changelogs-and-updates.html#setting-up-a-changelog" rel="nofollow noreferrer">Craft's documentation</a> on changelogs so I'm not sure what I'm missing. Is there anything else I can try or debug?</p>
  
Tags: <plugin-development><updates>
Title: Plugin not updating in the plugin store from changelog updates
ThreadText: # Plugin not updating in the plugin store from changelog updates
  
  (Asked by: username_0 on 2019-02-28)
  
  I have a [custom plugin](https://github.com/hillholliday/Craft-User-Manual/) registered with [id.craftcms.com](https://id.craftcms.com/).
  
  ![id.craft.cms changelog screenshot](https://cl.ly/368a5bd83718/Screen%20Shot%202019-02-28%20at%2010.46.10%20AM.jpg)
  
  The plugin store currently sees it at as 2.0.0, but I have since updated the plugin to 2.0.1 (and subsequently tried to force a silent 2.0.2 update) and noted so in my [changelog](https://github.com/hillholliday/Craft-User-Manual/blob/master/CHANGELOG.md) but the plugin store is not seeing this update.
  
  The contents of my changelog look like this:
  
  ```
  # Release Notes for Craft User Manual
  
  ## 2.0.2 - 2019-02-27
  ### Updated
  - Forcing new version for deprecation issues
  
  ## 2.0.1 - 2018-08-24
  ### Fixed
  - Deprecation Issues
  
  ## 2.0.0 - 2018-08-24
  ### Added
   - Initial Craft 3 release
  
  ```
  
  This was lifted directly from [Craft's documentation](https://docs.craftcms.com/v3/extend/changelogs-and-updates.html#setting-up-a-changelog) on changelogs so I'm not sure what I'm missing. Is there anything else I can try or debug?
  
  **Tags:** plugin-development, updates
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-03-01. Score: 1 | Accepted answer
  
  The reason the Plugin Store hasn't picked up the 2.0.1 release is that you've got 3 different 2.0.1 tags in the repo.
  
  [![enter image description here](https://i.sstatic.net/kXtZr.jpg)](https://i.sstatic.net/kXtZr.jpg)
  
  Usually, that's not a problem as it will just pick the first one by date.
  
  In this case, if you browse the first "V2.0.1" tag, you'll see that its composer.json file has a listed version of 2.0.0, which is a version mismatch, so the Plugin Store will ignore it. <https://github.com/hillholliday/Craft-User-Manual/blob/00e2808e328e5bfe793fd343a59b5d2445d84d27/composer.json#L5>
  
  The reasons 2.0.2 never got picked up is because there is no 2.0.2 tag in the repo.
  
  > **Comments:**
  > **username_0**: Thanks username_1, that makes perfect sense. I didn't realize the plugin store looked at git tags. I'll update accordingly.  
  
  ---
  
  