Merge pull request #2010 from strictdoc-project/stanislaw/itest_cache…

…_dir

Bump version to 0.3.0

docs/strictdoc_01_user_guide.sdoc

@@ -2357,6 +2357,10 @@ or
         print("Hello, World\n");
     }
 
+.. note::
+
+    For the C language, if a ``@relation marker`` is included in a function declaration prototype (which is the most common practice), StrictDoc also creates a link between the requirement and the corresponding C function definition.
+
 **4\) Linking a range to a requirement**
 
 .. code:: python

docs/strictdoc_04_release_notes.sdoc

@@ -24,6 +24,20 @@ STATEMENT: >>>
 This document maintains a record of all changes to StrictDoc since November 2023. It serves as a user-friendly version of the changelog, complementing the automatically generated, commit-by-commit changelog available here: `StrictDoc Changelog <https://github.com/strictdoc-project/strictdoc/blob/main/CHANGELOG.md>`_.
 <<<
 
+[SECTION]
+MID: 591c1b85c6fb4453aee08e23cb9f257a
+TITLE: 0.3.0 (2024-11-21)
+
+[TEXT]
+MID: b39a3b3d9f8640e380dad5a2fdb75d79
+STATEMENT: >>>
+This release includes an enhancement to the feature for tracing requirements to C source code.
+
+From now on, if a ``@relation`` marker is specified in a C function declaration, StrictDoc will perform its "magic" and automatically connect the referenced requirement to the corresponding C function definition. This allows a ``@relation`` marker to be placed in the main documentation block, typically located above C function declarations, while ensuring the requirement is also linked to the function definition.
+<<<
+
+[/SECTION]
+
 [SECTION]
 MID: f4cd860f07b1479ba1845bce3c749d68
 TITLE: 0.2.1 (2024-11-10)

strictdoc/__init__.py

@@ -1,6 +1,6 @@
 from strictdoc.core.environment import SDocRuntimeEnvironment
 
-__version__ = "0.2.1"
+__version__ = "0.3.0"
 
 
 environment = SDocRuntimeEnvironment(__file__)