docs/releases.md
<h2>Changelog</h2>
You can see the full log of changes for each release on our separate <a href="./changelog">changelog page</a>.
The migration guide covers what to think about when migrating to a new major version. Mostly, you should not really be practically affected by most of the major version jumps: it's mostly trivial stuff like dropping support for a version of Node or some very minute detail of an implementation some people might depend upon.
<div class="in-content releases"> <ul> {% assign sorted_releases = site.releases | sort: "sort_id" | reverse %} {% for release in sorted_releases %} {% assign url_parts = release.url | split: "/" %} {% comment %} Weird as hell, but .size == 3 means there are 2 elements ...
{% endcomment %}
{% if url_parts.size == 3 and url_parts[2] != "latest" %}
<li>
<p>
<span class="ver">{{ release.release_id }}</span>
<span class="pull-right">
<a
class="btn btn-primary"
href="{{site.baseurl}}/releases/sinon-{{ release.release_id | remove_first: 'v' }}.js"
>Download</a
>
<a
class="btn btn-default"
href="{{site.baseurl}}{{ release.url }}"
>Docs</a
>
</span>
</p>
</li>
{% endif %}
{% endfor %}
</ul>
{% comment %} vim: ft=liquid {%endcomment %}