diff --git a/edmarketconnector.xml b/edmarketconnector.xml
index 21fd6e6b..bb2e2188 100644
--- a/edmarketconnector.xml
+++ b/edmarketconnector.xml
@@ -36,7 +36,7 @@
 		<!-- Windows -->
 
 		<item>
-			<title>Release 5.1.2</title>
+			<title>Release 5.1.3</title>
 			<description>
 				<![CDATA[
 <style>body { font-family:"Segoe UI","Tahoma"; font-size: 75%; } h2 { font-family:"Segoe UI","Tahoma"; font-size: 105%; }</style>
@@ -58,6 +58,61 @@ currently used version in a given branch.</p>
 </li>
 </ul>
 
+<h2>Release 5.1.3</h2>
+<ul>
+<li>
+<p>Attempt to flush any pending EDSM API data when a Journal <code>Shutdown</code> or
+<code>Fileheader</code> event is seen.  After this, the data is dropped.  This ensures
+that, if the user next logs in to a different commander, the data isn't then
+sent to the wrong EDSM account.</p>
+</li>
+<li>
+<p>Ensure a previous Journal file is fully read/drained before starting
+processing of a new one.  In particular, this ensures properly seeing the end
+of a continued Journal file when opening the continuation file.</p>
+</li>
+<li>
+<p>New config options, in a new <code>Privacy</code> tab, to hide the current Private
+Group, or captain of a ship you're multi-crewing on.  These usually appear
+on the <code>Commander</code> line of the main UI, appended after your commander name,
+with a <code>/</code> between.</p>
+</li>
+<li>
+<p>EDO dockable settlement names with <code>+</code> characters appended will no longer
+cause 'server lagging' reports.</p>
+</li>
+<li>
+<p>Don't force DEBUG level logging to the
+<a href="https://github.com/EDCD/EDMarketConnector/wiki/Troubleshooting#plain-log-file">plain log file</a>
+if <code>--trace</code> isn't used to force TRACE level logging.  This means logging
+<em>to the plain log file</em> will once more respect the user-set Log Level, as in
+the Configuration tab of Settings.</p>
+<p>As its name implies, the <a href="https://github.com/EDCD/EDMarketConnector/wiki/Troubleshooting#debug-log-files">debug log file</a>
+will always contain at least DEBUG level logging, or TRACE if forced.</p>
+</li>
+</ul>
+<h2>
+<a id="user-content-plugin-developers" class="anchor" href="#plugin-developers" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>(Plugin) Developers</h2>
+<ul>
+<li>
+<p>New EDMarketConnector option <code>--trace-on ...</code> to control if certain TRACE
+level logging is used or not.  This helps keep the noise down whilst being
+able to have users activate choice bits of logging to help track down bugs.</p>
+<p>See <a href="Contributing.md#use-the-appropriate-logging-level">Contributing.md</a> for
+details.</p>
+</li>
+<li>
+<p>Loading of <code>ShipLocker.json</code> content is now tried up to 5 times, 10ms apart,
+if there is a file loading, or JSON decoding, failure.  This should
+hopefully result in the data being loaded correctly if a race condition with
+the game client actually writing to and closing the file is encountered.</p>
+</li>
+<li>
+<p><code>config.get_bool('some_str', default=SomeDefault)</code> will now actually honour
+that specified default.</p>
+</li>
+</ul>
+
 <h2>Release 5.1.2</h2>
 <ul>
 <li>
@@ -851,11 +906,11 @@ about this:
 				]]>
 			</description>
 			<enclosure
-				url="https://github.com/EDCD/EDMarketConnector/releases/download/Release/5.1.2/EDMarketConnector_win_5.1.2.msi"
+				url="https://github.com/EDCD/EDMarketConnector/releases/download/Release/5.1.3/EDMarketConnector_win_5.1.3.msi"
 				sparkle:os="windows"
 				sparkle:installerArguments="/passive LAUNCH=yes"
-				sparkle:version="5.1.2"
-				length="10170368"
+				sparkle:version="5.1.3"
+				length="10182656"
 				type="application/octet-stream"
 			/>
 		</item>