Release v0.30.2

Author: alexanderkiel

CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## v0.30.2
+
+### Performance
+
+* Improve FHIR Search Performance with Subject References ([#2161](https://github.com/samply/blaze/issues/2161))
+
+### Documentation
+
+* Add Note About Fix Context Path When Using the UI ([#2135](https://github.com/samply/blaze/issues/2135))
+
+The full changelog can be found [here](https://github.com/samply/blaze/milestone/102?closed=1).
+
 ## v0.30.1
 
 ### Bugfixes

Dockerfile

@@ -7,7 +7,7 @@ RUN apt-get update && apt-get upgrade -y && \
     rm -rf /var/lib/apt/lists/
 
 RUN mkdir -p /app/data && chown 1001:1001 /app/data
-COPY target/blaze-0.30.1-standalone.jar /app/
+COPY target/blaze-0.30.2-standalone.jar /app/
 
 WORKDIR /app
 USER 1001
@@ -20,4 +20,4 @@ ENV RESOURCE_DB_DIR="/app/data/resource"
 ENV ADMIN_INDEX_DB_DIR="/app/data/admin-index"
 ENV ADMIN_TRANSACTION_DB_DIR="/app/data/admin-transaction"
 
-CMD ["java", "-jar",  "blaze-0.30.1-standalone.jar"]
+CMD ["java", "-jar",  "blaze-0.30.2-standalone.jar"]

README.md

@@ -20,7 +20,7 @@ A demo installation can be found [here](https://blaze.life.uni-leipzig.de/fhir)
 
 Blaze is widely used in the [Medical Informatics Initiative](https://www.medizininformatik-initiative.de) in Germany and in [Biobanks](https://www.bbmri-eric.eu) across Europe. A 1.0 version is expected in the next months.
 
-Latest release: [v0.30.1][5]
+Latest release: [v0.30.2][5]
 
 ## Quick Start
 
@@ -76,7 +76,7 @@ Unless required by applicable law or agreed to in writing, software distributed
 
 [3]: <https://cql.hl7.org/tests.html>
 [4]: <https://alexanderkiel.gitbook.io/blaze/deployment>
-[5]: <https://github.com/samply/blaze/releases/tag/v0.30.1>
+[5]: <https://github.com/samply/blaze/releases/tag/v0.30.2>
 [6]: <https://www.yourkit.com/java/profiler/>
 [7]: <https://www.yourkit.com/.net/profiler/>
 [8]: <https://www.yourkit.com/youmonitor/>

build.clj

@@ -5,7 +5,7 @@
    [java.time LocalDate]))
 
 (def lib 'samply/blaze)
-(def version "0.30.1")
+(def version "0.30.2")
 (def class-dir "target/classes")
 (def basis (b/create-basis {:project "deps.edn"}))
 (def uber-file (format "target/%s-%s-standalone.jar" (name lib) version))

docs/.vitepress/config.ts

@@ -27,7 +27,7 @@ export default defineConfig({
         nav: [
             {text: 'Home', link: '/'},
             {
-                text: "v0.30.1",
+                text: "v0.30.2",
                 items: [
                     {
                         text: 'Changelog',

docs/deployment/manual-deployment.md

@@ -2,12 +2,12 @@
 
 The installation works under Windows, Linux and macOS. The only dependency is an installed OpenJDK 11 or 17 with 17 recommended. Blaze is tested with [Eclipse Temurin][1].
 
-Blaze runs on the JVM and comes as single JAR file. Download the most recent version [here](https://github.com/samply/blaze/releases/tag/v0.30.1). Look for `blaze-0.30.1-standalone.jar`.
+Blaze runs on the JVM and comes as single JAR file. Download the most recent version [here](https://github.com/samply/blaze/releases/tag/v0.30.2). Look for `blaze-0.30.2-standalone.jar`.
 
 After the download, you can start blaze with the following command (Linux, macOS):
 
 ```sh
-java -jar blaze-0.30.1-standalone.jar
+java -jar blaze-0.30.2-standalone.jar
 ```
 
 Blaze will run with an in-memory, volatile database for testing and demo purposes.
@@ -17,14 +17,14 @@ Blaze can be run with durable storage by setting the environment variables `STOR
 Under Linux/macOS:
 
 ```sh
-STORAGE=standalone java -jar blaze-0.30.1-standalone.jar
+STORAGE=standalone java -jar blaze-0.30.2-standalone.jar
 ```
 
 Under Windows, you need to set the Environment variables in the PowerShell before starting Blaze:
 
 ```powershell
 $Env:STORAGE="standalone"
-java -jar blaze-0.30.1-standalone.jar
+java -jar blaze-0.30.2-standalone.jar
 ```
 
 This will create three directories called `index`, `transaction` and `resource` inside the current working directory, one for each database part used.
@@ -42,7 +42,7 @@ The output should look like this:
 2021-06-27T11:02:37.834Z ee086ef908c1 main INFO [blaze.core:64] - JVM version: 16.0.2
 2021-06-27T11:02:37.834Z ee086ef908c1 main INFO [blaze.core:65] - Maximum available memory: 1738 MiB
 2021-06-27T11:02:37.835Z ee086ef908c1 main INFO [blaze.core:66] - Number of available processors: 8
-2021-06-27T11:02:37.836Z ee086ef908c1 main INFO [blaze.core:67] - Successfully started Blaze version 0.30.1 in 8.2 seconds
+2021-06-27T11:02:37.836Z ee086ef908c1 main INFO [blaze.core:67] - Successfully started Blaze version 0.30.2 in 8.2 seconds
 ```
 
 In order to test connectivity, query the health endpoint:
@@ -62,7 +62,7 @@ that should return:
 ```json
 {
   "name": "Blaze",
-  "version": "0.30.1"
+  "version": "0.30.2"
 }
 ```
 

docs/deployment/standalone-backend.md

@@ -27,7 +27,7 @@ Blaze should log something like this:
 2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:67] - JVM version: 17.0.7
 2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:68] - Maximum available memory: 1738 MiB
 2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:69] - Number of available processors: 2
-2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:70] - Successfully started 🔥 Blaze version 0.30.1 in 9.0 seconds
+2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:70] - Successfully started 🔥 Blaze version 0.30.2 in 9.0 seconds
 ```
 
 In order to test connectivity, query the health endpoint:
@@ -47,7 +47,7 @@ that should return:
 ```json
 {
   "name": "Blaze",
-  "version": "0.30.1"
+  "version": "0.30.2"
 }
 ```