From af12816efbbc4fb6b430e69300332d2de2504be6 Mon Sep 17 00:00:00 2001 From: Athanasius Date: Wed, 26 Aug 2020 14:34:56 +0100 Subject: [PATCH] Release 4.0.5: version, changelog, appcast --- ChangeLog.md | 30 ++++++++++++++++++++++++++++++ config.py | 2 +- edmarketconnector.xml | 42 ++++++++++++++++++++++++++++++++++++++---- 3 files changed, 69 insertions(+), 5 deletions(-) diff --git a/ChangeLog.md b/ChangeLog.md index 1c5c7701..250a545f 100644 --- a/ChangeLog.md +++ b/ChangeLog.md @@ -1,6 +1,36 @@ This is the master changelog for Elite Dangerous Market Connector. Entries are in reverse chronological order (latest first). --- +Release 4.0.5 +=== + + * Built using Python 3.7.9. + * Fix EDSM plugin so the System provider actually updates the URLs for + jumps to new systems. + + In general this cleans up the code for all three System and Station Providers; + EDDB, EDSM, Inara. + +Release 4.0.4 +=== + + * Built using Python 3.7.8. Prior 4.0.x releases used 3.7.7. + * Don't crash if no non-default Journal Directory has been set. + * Only send to Inara API at most once every 30 seconds. This should avoid + the "Inara 400 Too much requests, slow down, cowboy. ;) ..." message and + being locked out from the API for an hour as a result. Any events that + require data to be sent during the 30s cooldown will be queued and sent when + that timer expires. + + This was caused by previous changes in an attempt to send cargo events + to Inara more often. This fix retains that enhancement. + + Note that if you log out and stop EDMC within 30 seconds you might have + some events not sent. If we tried to force a send then it might hit the + limit when you want to log back in and continue playing. As it is you can + re-run EDMC and log back into the game to ensure Inara is synchronised + properly. + Release 4.0.3 === diff --git a/config.py b/config.py index b0b887ec..568178ac 100644 --- a/config.py +++ b/config.py @@ -13,7 +13,7 @@ appcmdname = 'EDMC' # appversion **MUST** follow Semantic Versioning rules: # # Major.Minor.Patch(-prerelease)(+buildmetadata) -appversion = '4.0.3' #-rc1+a872b5f' +appversion = '4.0.5' #-rc1+a872b5f' # For some things we want appversion without (possible) +build metadata appversion_nobuild = str(semantic_version.Version(appversion).truncate('prerelease')) copyright = u'© 2015-2019 Jonathan Harris, 2020 EDCD' diff --git a/edmarketconnector.xml b/edmarketconnector.xml index 1ad38955..e2491386 100644 --- a/edmarketconnector.xml +++ b/edmarketconnector.xml @@ -168,11 +168,45 @@ - Release 4.0.3 + Release 4.0.5 body { font-family:"Segoe UI","Tahoma"; font-size: 75%; } h2 { font-family:"Segoe UI","Tahoma"; font-size: 105%; } +

Release 4.0.5

+
    +
  • Built using Python 3.7.9.
    • +
  • Fix EDSM plugin so the System provider actually updates the URLs for +jumps to new systems.
    • +
+

In general this cleans up the code for all three System and Station Providers; +EDDB, EDSM, Inara.

+ +

Release 4.0.4

+
    +
  • +

    Built using Python 3.7.8. Prior 4.0.x releases used 3.7.7.

    +
    • +
  • +

    Don't crash if no non-default Journal Directory has been set.

    +
    • +
  • +

    Only send to Inara API at most once every 30 seconds. This should avoid +the "Inara 400 Too much requests, slow down, cowboy. ;) ..." message and +being locked out from the API for an hour as a result. Any events that +require data to be sent during the 30s cooldown will be queued and sent when +that timer expires.

    +

    This was caused by previous changes in an attempt to send cargo events +to Inara more often. This fix retains that enhancement.

    +

    Note that if you log out and stop EDMC within 30 seconds you might have +some events not sent. If we tried to force a send then it might hit the +limit when you want to log back in and continue playing. As it is you can +re-run EDMC and log back into the game to ensure Inara is synchronised +properly.

    +
    • +
+ +

Release 4.0.3

NB: Anyone who installed a 4.0.3-rcX release candidate version should first uninstall it before installing this. @@ -578,11 +612,11 @@ If any of your plugins are listed in that section then they will need updating, ]]>