chore: bump snapshot version

gradle.properties

@@ -13,8 +13,8 @@ systemProp.sonar.projectKey=graphs4value_refinery
 systemProp.sonar.organization=graphs4value
 systemProp.sonar.host.url=https://sonarcloud.io
 tools.refinery.interpreter.group=tools.refinery.interpreter
-tools.refinery.interpreter.release=0.29.1-2
+tools.refinery.interpreter.release=0.29.1-3
 # Follow the VIATRA incubation versioning scheme to avoid breaking SemVer.
-tools.refinery.interpreter.version=0.29.1-3
-tools.refinery.release=0.1.3
-version=0.1.4
+tools.refinery.interpreter.version=0.30.0-1-SNAPSHOT
+tools.refinery.release=0.1.4
+version=0.1.5-SNAPSHOT

subprojects/docs/versioned_docs/version-0.1.3/develop/java.md → subprojects/docs/versioned_docs/version-0.1.4/develop/java.md

@@ -33,14 +33,14 @@ import Tabs from '@theme/Tabs';
   <TabItem value="kotlin" label="Kotlin">
     ```kotlin title="settings.gradle.kts"
     plugins {
-        id("tools.refinery.settings") version "0.1.3"
+        id("tools.refinery.settings") version "0.1.4"
     }
     ```
   </TabItem>
   <TabItem value="groovy" label="Groovy">
     ```groovy title="settings.gradle"
     plugins {
-        id 'tools.refinery.settings' version '0.1.3'
+        id 'tools.refinery.settings' version '0.1.4'
     }
     ```
   </TabItem>
@@ -320,7 +320,7 @@ You should add the following configuration to your `pom.xml` file. If you use mu
             <dependency>
                 <groupId>tools.refinery</groupId>
                 <artifactId>refinery-bom</artifactId>
-                <version>0.1.3</version>
+                <version>0.1.4</version>
                 <type>pom</type>
                 <scope>import</scope>
             </dependency>

subprojects/docs/versioned_docs/version-0.1.3/develop/javadoc.md → subprojects/docs/versioned_docs/version-0.1.4/develop/javadoc.md

@@ -11,21 +11,21 @@ Here you can find API documentation for Refinery components automatically genera
 
 # Refinery
 
-* [`tools.refinery:refinery-generator:0.1.3`](pathname://refinery-generator/)
-* [`tools.refinery:refinery-gradle-plugins:0.1.3`](pathname://refinery-gradle-plugins/)
-* [`tools.refinery:refinery-language:0.1.3`](pathname://refinery-language/)
-* [`tools.refinery:refinery-language-ide:0.1.3`](pathname://refinery-language-ide/)
-* [`tools.refinery:refinery-language-model:0.1.3`](pathname://refinery-language-model/)
-* [`tools.refinery:refinery-language-semantics:0.1.3`](pathname://refinery-language-semantics/)
-* [`tools.refinery:refinery-logic:0.1.3`](pathname://refinery-logic/)
-* [`tools.refinery:refinery-store:0.1.3`](pathname://refinery-store/)
-* [`tools.refinery:refinery-store-dse:0.1.3`](pathname://refinery-store-dse/)
-* [`tools.refinery:refinery-store-dse-visualization:0.1.3`](pathname://refinery-store-dse-visualization/)
-* [`tools.refinery:refinery-store-query:0.1.3`](pathname://refinery-store-query/)
-* [`tools.refinery:refinery-store-query-interpreter:0.1.3`](pathname://refinery-store-query-interpreter/)
-* [`tools.refinery:refinery-store-reasoning:0.1.3`](pathname://refinery-store-reasoning/)
-* [`tools.refinery:refinery-store-reasoning-scope:0.1.3`](pathname://refinery-store-reasoning-scope/)
-* [`tools.refinery:refinery-store-reasoning-smt:0.1.3`](pathname://refinery-store-reasoning-smt/)
+* [`tools.refinery:refinery-generator:0.1.4`](pathname://refinery-generator/)
+* [`tools.refinery:refinery-gradle-plugins:0.1.4`](pathname://refinery-gradle-plugins/)
+* [`tools.refinery:refinery-language:0.1.4`](pathname://refinery-language/)
+* [`tools.refinery:refinery-language-ide:0.1.4`](pathname://refinery-language-ide/)
+* [`tools.refinery:refinery-language-model:0.1.4`](pathname://refinery-language-model/)
+* [`tools.refinery:refinery-language-semantics:0.1.4`](pathname://refinery-language-semantics/)
+* [`tools.refinery:refinery-logic:0.1.4`](pathname://refinery-logic/)
+* [`tools.refinery:refinery-store:0.1.4`](pathname://refinery-store/)
+* [`tools.refinery:refinery-store-dse:0.1.4`](pathname://refinery-store-dse/)
+* [`tools.refinery:refinery-store-dse-visualization:0.1.4`](pathname://refinery-store-dse-visualization/)
+* [`tools.refinery:refinery-store-query:0.1.4`](pathname://refinery-store-query/)
+* [`tools.refinery:refinery-store-query-interpreter:0.1.4`](pathname://refinery-store-query-interpreter/)
+* [`tools.refinery:refinery-store-reasoning:0.1.4`](pathname://refinery-store-reasoning/)
+* [`tools.refinery:refinery-store-reasoning-scope:0.1.4`](pathname://refinery-store-reasoning-scope/)
+* [`tools.refinery:refinery-store-reasoning-smt:0.1.4`](pathname://refinery-store-reasoning-smt/)
 
 # Interpreter
 
@@ -35,7 +35,7 @@ The _Refinery Interpreter_ is modified version of [VIATRA™](https://eclips
 
 :::
 
-* [`tools.refinery.interpreter:refinery-interpreter:0.29.1-2`](pathname://refinery-interpreter/)
-* [`tools.refinery.interpreter:refinery-interpreter-localsearch:0.29.1-2`](pathname://refinery-interpreter-localsearch/)
-* [`tools.refinery.interpreter:refinery-interpreter-rete:0.29.1-2`](pathname://refinery-interpreter-rete/)
-* [`tools.refinery.interpreter:refinery-interpreter-rete-recipes:0.29.1-2`](pathname://refinery-interpreter-rete-recipes/)
+* [`tools.refinery.interpreter:refinery-interpreter:0.29.1-3`](pathname://refinery-interpreter/)
+* [`tools.refinery.interpreter:refinery-interpreter-localsearch:0.29.1-3`](pathname://refinery-interpreter-localsearch/)
+* [`tools.refinery.interpreter:refinery-interpreter-rete:0.29.1-3`](pathname://refinery-interpreter-rete/)
+* [`tools.refinery.interpreter:refinery-interpreter-rete-recipes:0.29.1-3`](pathname://refinery-interpreter-rete-recipes/)

subprojects/docs/versioned_docs/version-0.1.3/learn/docker/cli.md → subprojects/docs/versioned_docs/version-0.1.4/learn/docker/cli.md

@@ -10,7 +10,7 @@ sidebar_label: CLI
 You can run Refinery as a command-line applications via our [Docker container](https://github.com/graphs4value/refinery/pkgs/container/refinery-cli) on either `amd64` or `arm64` machines:
 
 ```shell
-docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.3
+docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.4
 ```
 
 This will let you read input files and generate models in the current directory (`${PWD}`) of your terminal session.
@@ -19,13 +19,13 @@ Module imports (e.g., `import some::module.` to import `some/module.refinery`) r
 For example, to generate a model based on the file named `input.problem` in the current directory and write the results into the file named `output.refinery`, you may run the [`generate` subcommand](#generate) with
 
 ```shell
-docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.3 generate -o output.refinery input.problem
+docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.4 generate -o output.refinery input.problem
 ```
 
 If you want Refinery CLI to print its documentation, run
 
 ```shell
-docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.3 -help
+docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.4 -help
 ```
 
 ## The `generate` subcommand {#generate}
@@ -34,7 +34,7 @@ The `generate` subcommand generates a consistent concrete model from a partial m
 You can also use the short name `g` to access this subcommand.
 
 ```shell
-docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.3 generate [options] input path
+docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.4 generate [options] input path
 ```
 
 The `input path` should be a path to a `.problem` file relative to the current directory.
@@ -74,7 +74,7 @@ This option is especially useful if you want to generate models of multiple size
 For example, the command
 
 ```shell
-docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.3 generate -s File=20..25 input.problem
+docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.4 generate -s File=20..25 input.problem
 ```
 
 is equivalent to appending
@@ -154,7 +154,7 @@ The `check` subcommand checks a partial model for inconsistencies.
 * For partial models that can't be constructed due to **syntax or propagation errors**, it prints and error message to the standard output and sets the exit value to `1`.
 
 ```shell
-docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.3 check [options] input path
+docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.4 check [options] input path
 ```
 
 The `input path` should be a path to a `.problem` or `.refinery` file relative to the current directory.
@@ -180,7 +180,7 @@ If the result of the concretization is inconsistent, it shows an error with a fo
 Scope constraints will likely render your partial model inconsistent after concretization if they prescribe multiple nodes to be created. You should the required nodes manually to the model or remove the scope constraints before concretization.
 
 ```shell
-docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.3 concretize [options] input path
+docker run --rm -it -v ${PWD}:/data ghcr.io/graphs4value/refinery-cli:0.1.4 concretize [options] input path
 ```
 
 The `input path` should be a path to a `.problem` or `.refinery` file relative to the current directory.

subprojects/docs/versioned_docs/version-0.1.3/learn/docker/index.md → subprojects/docs/versioned_docs/version-0.1.4/learn/docker/index.md

@@ -24,7 +24,7 @@ Installing Refinery as a Docker container can support more advanced use cases, s
 To generate larger models with a longer timeout, you can use our [Docker container](https://github.com/graphs4value/refinery/pkgs/container/refinery) on either `amd64` or `arm64` machines:
 
 ```shell
-docker run --rm -it -p 8888:8888 ghcr.io/graphs4value/refinery:0.1.3
+docker run --rm -it -p 8888:8888 ghcr.io/graphs4value/refinery:0.1.4
 ```
 
 Once Docker pulls and starts the container, you can navigate to http://localhost:8888 to open the model generation interface and start editing.

subprojects/docs/versions.json

@@ -1,4 +1,4 @@
 [
-  "0.1.3",
+  "0.1.4",
   "0.1.0"
 ]