Do not use incomming release when looking for latest release

assigned to @gbonnefille

@luc it seems related to the fact that you prepared the next release directly on master branch and not on develop branch. Is it really what it is expected?

I did this on the develop branch.

(lehrin) luc% git show HEAD
commit 7efdf497672962452b52f8aa9b875d8ccfab094c (HEAD -> develop, origin/develop)
Author: Luc Maisonobe <luc@orekit.org>
Date:   Mon Jul 4 09:17:03 2022 +0200

    Announced Rugged 3.0.

diff --git a/_posts/2022-07-0.3-rugged-3.0-released.md b/_posts/2022-07-0.3-rugged-3.0-released.md
new file mode 100644
index 0000000..a9a95d9
--- /dev/null
+++ b/_posts/2022-07-0.3-rugged-3.0-released.md
@@ -0,0 +1,20 @@
+---
+title: "Rugged 3.0 released"
+excerpt: "New Rugged version released, updated to latest Orekit and Hipparchus"
+layout: post_rugged
+publication_year: 2022
+date: 2022-07-03 20:27:00 +0200
+modified: 2022-07-03 20:27:00 +0200
+project: rugged
+categories:
+- News
+tags:
+- news
+- release
+---
+
+Version 3.0 is a major release.
+
+  - Fixed longitude normalization issue with tiles
+  - Fixed inverse location issue with atmospheric refraction
+  - Updated dependencies to Orekit 11.2 and Hipparchus 2.1
(lehrin) luc% 

Yes, sorry: the mater is on the Rugged's history. See rugged@fc87980f