Using new versions of docs-as-code

MODULE.bazel

@@ -35,9 +35,9 @@ bazel_dep(name = "buildifier_prebuilt", version = "8.5.1")
 bazel_dep(name = "platforms", version = "1.0.0")
 
 # S-CORE process rules
-bazel_dep(name = "score_bazel_platforms", version = "0.1.2")
+bazel_dep(name = "score_bazel_platforms", version = "1.0.0")
 
-bazel_dep(name = "score_docs_as_code", version = "4.6.0", dev_dependency = True)
+bazel_dep(name = "score_docs_as_code", version = "7.1.0", dev_dependency = True)
 
 bazel_dep(name = "score_tooling", version = "1.2.0")
 single_version_override(
@@ -47,8 +47,8 @@ single_version_override(
 
 bazel_dep(name = "score_rust_policies", version = "0.0.5")
 
-bazel_dep(name = "score_process", version = "1.5.4", dev_dependency = True)
-bazel_dep(name = "score_platform", version = "0.6.0", dev_dependency = True)
+bazel_dep(name = "score_process", version = "2.0.3", dev_dependency = True)
+bazel_dep(name = "score_platform", version = "0.6.4", dev_dependency = True)
 bazel_dep(name = "score_itf", version = "0.5.0", dev_dependency = True)
 
 # OCI / Docker image rules for integration tests

docs/components/datarouter/index.rst

@@ -18,6 +18,7 @@ Datarouter
 
 .. comp:: Datarouter
    :id: comp__datarouter
+   :version: 1
    :security: YES
    :safety: QM
    :status: valid

docs/components/datarouter/requirements/index.rst

@@ -17,6 +17,7 @@ Datarouter Component Requirements
 
 .. document:: Datarouter Component Requirements
    :id: doc__data_router_requirements
+   :version: 1
    :status: valid
    :safety: QM
    :security: NO
@@ -27,24 +28,26 @@ Datarouter Services
 
 .. comp_req:: Datarouter DLT Server
    :id: comp_req__data_router__dlt_server
+   :version: 1
    :reqtype: Functional
    :security: NO
    :safety: QM
    :derived_from: feat_req__logging__compat_dlt, feat_req__logging__log_sinks_network
    :status: valid
-   :belongs_to: comp__datarouter
+   :satisfied_by: comp__datarouter
 
    Datarouter shall implement DLT server component. Datarouter provides the functionality to
    send messages using DLT protocol over UDP multicast transport.
 
 .. comp_req:: DLT Multiple Channel Support
    :id: comp_req__data_router__dlt_multiple_channels
+   :version: 1
    :reqtype: Functional
    :security: NO
    :safety: QM
    :derived_from: feat_req__logging__compat_dlt, feat_req__logging__config_log_filter, feat_req__logging__config_entity_id
    :status: valid
-   :belongs_to: comp__datarouter
+   :satisfied_by: comp__datarouter
 
    DLT server shall support multiple log channels as specified in AUTOSAR Diagnostic, Log and
    Trace Protocol Specification. The following parameters shall be configurable statically via
@@ -55,12 +58,13 @@ Datarouter Services
 
 .. comp_req:: DLT Message Filtering
    :id: comp_req__data_router__dlt_message_filtering
+   :version: 1
    :reqtype: Functional
    :security: NO
    :safety: QM
    :derived_from: feat_req__logging__filtering_log_levels, feat_req__logging__filtering_entity_id, feat_req__logging__config_log_filter
    :status: valid
-   :belongs_to: comp__datarouter
+   :satisfied_by: comp__datarouter
 
    DLT server shall support filtering of messages within each channel. The filter shall be
    parametrized with application ID, context ID, log level threshold. Initial filter set shall
@@ -69,12 +73,13 @@ Datarouter Services
 
 .. comp_req:: DLT Verbose Messages
    :id: comp_req__data_router__dlt_verbose_messages
+   :version: 1
    :reqtype: Functional
    :security: NO
    :safety: QM
    :derived_from: feat_req__logging__compat_dlt
    :status: valid
-   :belongs_to: comp__datarouter
+   :satisfied_by: comp__datarouter
 
    DLT server shall provide support for verbose DLT messages. Messages sent from mw::log
    library shall be sent via DLT using verbose mode.
@@ -84,24 +89,26 @@ DLT Quotas
 
 .. comp_req:: DLT Bandwidth Quota Configuration
    :id: comp_req__data_router__dlt_bw_quota_config
+   :version: 1
    :reqtype: Functional
    :security: NO
    :safety: QM
    :derived_from: feat_req__logging__config_buffer_size, feat_req__logging__resource_comm_channel
    :status: valid
-   :belongs_to: comp__datarouter
+   :satisfied_by: comp__datarouter
 
    The component shall have the DLT bandwidth quota configuration in the file located at
    ``./etc/log-channels.json`` relative to the application specific location ``/opt/``.
 
 .. comp_req:: DLT Quota Bandwidth Reduction
    :id: comp_req__data_router__dlt_quota_bw_reduction
+   :version: 1
    :reqtype: Functional
    :security: NO
    :safety: QM
    :derived_from: feat_req__logging__message_loss_handling, feat_req__logging__qos_message_handling
    :status: valid
-   :belongs_to: comp__datarouter
+   :satisfied_by: comp__datarouter
 
    It shall be possible to configure the action to drop DLT messages when a quota is exceeded.
 

docs/components/mw_log/design_decisions/explicit_init.rst

@@ -3,6 +3,7 @@ Explicit initialization of logging
 
 .. dec_rec:: Explicit initialization of logging
    :id: dec_rec__log__explicit_init
+   :version: 1
    :status: proposed
    :context: See below.
    :decision: TBA

docs/components/mw_log/index.rst

@@ -18,6 +18,7 @@ mw::log
 
 .. comp:: Logging Component
    :id: comp__mw_logging
+   :version: 1
    :security: YES
    :safety: ASIL_B
    :status: valid