html/CHANGELOG.html in wwwjdic-13.0.0 vs html/CHANGELOG.html in wwwjdic-13.0.1
- old
+ new
@@ -2,11 +2,11 @@
<html>
<head>
<meta charset="UTF-8">
-<title>CHANGELOG - wwwjdic 13.0.0</title>
+<title>CHANGELOG - wwwjdic 13.0.1</title>
<script type="text/javascript">
var rdoc_rel_prefix = "./";
var index_rel_prefix = "./";
</script>
@@ -55,10 +55,11 @@
<div class="nav-section">
<h3>Table of Contents</h3>
<ul class="link-list" role="directory">
+ <li><a href="#label-Version+13.0.1">Version 13.0.1</a>
<li><a href="#label-Version+13.0.0">Version 13.0.0</a>
<li><a href="#label-Version+12.0.0">Version 12.0.0</a>
<li><a href="#label-Version+11.0.0">Version 11.0.0</a>
<li><a href="#label-Version+10.0.0">Version 10.0.0</a>
<li><a href="#label-Version+9.3.0">Version 9.3.0</a>
@@ -130,9 +131,22 @@
</div>
</nav>
<main role="main" aria-label="Page CHANGELOG">
+
+<h1 id="label-Version+13.0.1">Version 13.0.1<span><a href="#label-Version+13.0.1">¶</a> <a href="#top">↑</a></span></h1>
+
+<pre>* PATCH updating gem dependencies.
+* IN PROGRESS: translation example.
+* IN PROGRESS: restoring key configuration as allowed parameter, to
+ allow user asking for specific searches. Search key currently fixed
+ to 'Q' (exact match) type search.
+* IN PROGRESS: improving application RDoc to better comply with SemVer
+ point 1 (Software using Semantic Versioning MUST declare a public
+ API. This API could be declared in the code itself or exist strictly
+ in documentation. However it is done, it should be precise and
+ comprehensive.)</pre>
<h1 id="label-Version+13.0.0">Version 13.0.0<span><a href="#label-Version+13.0.0">¶</a> <a href="#top">↑</a></span></h1>
<pre>* MAJOR moving from a_gem.required_ruby_version = '~> 2.5' to
a_gem.required_ruby_version = '~> 2.6'.