<p>It looks like you have some en dashes <code>–</code> instead of hyphens <code>-</code> in your CHANGELOG.md version headings. These are probably causing some parsing issues.</p>

<p>Notice how there’s also no release date shown in the update utility.</p>

CC BY-SA 4.0
2018-07-19T14:47:30.883Z
The ever-observant @carlcs :) You might be right – I corrected the dashes to hyphens and pushed to Git; didn't help (I cleared out my /storage dir to make sure Craft didn't pull from a local cache), but the old changelog might be cached on P&T's end?
Mats Mikkel Rummelhoff
CC BY-SA 4.0
2018-07-19T16:04:41.513Z
Yeah they must be caching them. So what you have to do now is to add some more awesome features to the plugin and push a new release. Pretty sure that’s a good way to make them pull your updated changelogs…
carlcs
CC BY-SA 4.0
2018-07-19T19:10:23.723Z
Yes, but the plugin is already *perfect*. Maybe I'll just _remove_ some features. That'll show 'em.
Mats Mikkel Rummelhoff
CC BY-SA 4.0
2018-07-20T07:07:52.123Z
Or that, nobody needs perfection.
carlcs
CC BY-SA 4.0
2018-07-21T09:51:30.233Z
Fixed a bug, pushed a new release and Craft is displaying my changelog details now. Cheers @carlcs!
Mats Mikkel Rummelhoff
CC BY-SA 4.0
2018-07-19T10:58:09.990Z
2018-07-19T10:58:09.990Z
carlcs
<p>I can't figure out why Craft won't display my plugin's changelog details as expandable version headers, like it does for other plugins. I assume there's something wrong with the formatting in my CHANGELOG.md file, but I can't spot it.</p>

<p>The below screenshot is how my CHANGELOG.md renders inside Craft's update utility – notice that the version headers aren't expandable, which means there's no way to actually read the details for each version update:</p>

<p><a href="https://i.sstatic.net/fwDk2.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/fwDk2.png" alt="enter image description here"></a></p>

<p>The raw CHANGELOG markdown can be found here: <a href="https://raw.githubusercontent.com/mmikkel/Retcon-Craft/master/CHANGELOG.md" rel="nofollow noreferrer">https://raw.githubusercontent.com/mmikkel/Retcon-Craft/master/CHANGELOG.md</a></p>

<p>The <code>changelogUrl</code> attribute in the plugin's <a href="https://raw.githubusercontent.com/mmikkel/Retcon-Craft/master/composer.json" rel="nofollow noreferrer"><code>composer.json</code></a> file is correct.</p>

<plugin-development>
Why isn't Craft displaying my plugin's changelog details?
# Why isn't Craft displaying my plugin's changelog details?

(Asked by: username_0 on 2018-07-19)

I can't figure out why Craft won't display my plugin's changelog details as expandable version headers, like it does for other plugins. I assume there's something wrong with the formatting in my CHANGELOG.md file, but I can't spot it.

The below screenshot is how my CHANGELOG.md renders inside Craft's update utility – notice that the version headers aren't expandable, which means there's no way to actually read the details for each version update:

[![enter image description here](https://i.sstatic.net/fwDk2.png)](https://i.sstatic.net/fwDk2.png)

The raw CHANGELOG markdown can be found here: <https://raw.githubusercontent.com/mmikkel/Retcon-Craft/master/CHANGELOG.md>

The `changelogUrl` attribute in the plugin's [`composer.json`](https://raw.githubusercontent.com/mmikkel/Retcon-Craft/master/composer.json) file is correct.

**Tags:** plugin-development

---

## 1 answers

### Answer by username_1 on 2018-07-19. Score: 3 | Accepted answer

It looks like you have some en dashes `–` instead of hyphens `-` in your CHANGELOG.md version headings. These are probably causing some parsing issues.

Notice how there’s also no release date shown in the update utility.

> **Comments:**
> **username_0**: The ever-observant @carlcs :) You might be right – I corrected the dashes to hyphens and pushed to Git; didn't help (I cleared out my /storage dir to make sure Craft didn't pull from a local cache), but the old changelog might be cached on P&T's end?  
> **username_1**: Yeah they must be caching them. So what you have to do now is to add some more awesome features to the plugin and push a new release. Pretty sure that’s a good way to make them pull your updated changelogs…  
> **username_0**: Yes, but the plugin is already *perfect*. Maybe I'll just _remove_ some features. That'll show 'em.  
> **username_1**: Or that, nobody needs perfection.  
> **username_0**: Fixed a bug, pushed a new release and Craft is displaying my changelog details now. Cheers @carlcs!  

---

