### Description of the bug: Neue Versionen von Routingdienst und Routing API werden aktuell im Routingdienst nicht gepflegt. Der auf der Test-Umgebung betriebene Routingdienst gibt im Endpunkt https://routing-api-testing.fit-connect.fitko.dev/actuator/info aktuell an, Version `1.0.0` des **Routingdienstes** zu sein: ```json { "git": { "commit": { "id": { "abbrev": "d68bbe5" }, "time": "2023-02-20T09:27:58Z" }, "tags": "1.0.0" } } ``` Tatsächlich läuft dort jedoch eine neuere Version. Der auf der Test-Umgebung betriebene Routingdienst stellt die Version `1.1.0-rc2` der **Routing API** bereit. Im Endpunkt https://routing-api-testing.fit-connect.fitko.dev/v1/info ist jedoch noch die Version `1.0.0` angegeben: ```json { "version": { "major": 1, "minor": 0, "patch": 0 } } ``` ### Current behavior: - see above ### Expected behavior: 1. [x] Im Endpunkt https://routing-api-testing.fit-connect.fitko.dev/actuator/info wird die tatsächliche Version des Routingdienstes ausgegeben. 2. [x] Im Endpunkt https://routing-api-testing.fit-connect.fitko.dev/v1/info wird die tatsächlich implementierte Version der Routing API ausgegeben. 3. [x] Es ist sichergestellt, dass zukünftig immer die jeweils aktuellen Versionen ausgegeben werden (z.B. durch Festlegung der Versionen im Build-Prozess). ### Environments: <!-- Specify here which environments are affected, e.g. DEV, TEST, STAGE, PROD --> - TEST-Umgebung - PROD-Umgebung ### Additional Information: <!-- Enter further relevant information here, e.g. operating system, browser etc. including the version of the FIT-Connect component --> ### Dependency / relationship to other issues: <!-- Write down here what kind of relationship it is and a brief explanation of it. --> ### Responsible person / team: <!-- Insert here the name of the person or team responsible for processing the bug. --> ### Contact persons including contact details: <!-- Indication of contact persons such as the person who reported the error, how to reach them. --> ### Screenshots / Logs / Requests: <!-- Insert screenshots or other (visual) aids here if necessary to clarify the bug. --> ### Checklist: - [x] Add Severity label - [x] Add team label - [x] Related/affected issues/stories/epics linked and explained in the bug issue - [ ] Creation of an automated test - [x] Bugfix deployed on DEV - [ ] Bugfix tested on DEV - [x] Bugfix deployed on TEST - [ ] Bugfix tested on TEST (possibly also by the connection project itself) - [ ] Successful fix reported to Team Operations (Teams channel) - [x] Bugfix deployed on STAGE - [ ] Bugfix tested on STAGE if necessary - [x] Bugfix deployed on PROD - [ ] Bugfix tested on PROD (possibly also by the connection project itself) - [ ] Final communication by Team Operations if necessary - [ ] Internal documentation was checked and updated if necessary - [ ] External documentation has been checked and updated if necessary - [ ] Updated changelog if necessary ### Approach/Solution: <!-- Other comments or notes can be added here, e.g. what has been tried so far to solve the problem. --> ### Release version of the artifact: