docs(changelog): update changelog for v0.6.3 (#368)

* update changelog for v0.6.3

Signed-off-by: ISP akm <akm@isp.co.jp>

* ci(pre-commit): autofix

* avoid spell miss

Signed-off-by: ISP akm <akm@isp.co.jp>

---------

Signed-off-by: ISP akm <akm@isp.co.jp>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

Author: xygyo77

docs/changelog.md

@@ -2,6 +2,38 @@
 
 ## CARET
 
+### v0.6.3 <small>\_ Aug 01, 2025</small> {id = "0.6.3"}
+
+- **Update**: exclude 3.7.0 from bokeh installation. ([caret_analyze #558](https://github.com/tier4/caret_analyze/pull/558))
+
+- **Feat**: accelerate graph search and cached method. ([caret_analyze #554](https://github.com/tier4/caret_analyze/pull/554))
+
+- **Update**: add topic_tools to the caret release script. ([caret #212](https://github.com/tier4/caret/pull/212))
+
+- **Update**: overhaul of docstrings(runtime, plot, value_objects). ([caret_analyze #553](https://github.com/tier4/caret_analyze/pull/553))
+
+- **Refactor**: refactor frequency calculation logic. ([caret_analyze #560](https://github.com/tier4/caret_analyze/pull/560))
+
+- **Update**: overhaul of docstrings(architecture). ([caret_analyze #559](https://github.com/tier4/caret_analyze/pull/559))
+
+- **Update**: overhaul of docstrings(infra). ([caret_analyze #561](https://github.com/tier4/caret_analyze/pull/561))
+
+- **Fix**: ignore setuptools 80.0.0. ([caret_analyze #565](https://github.com/tier4/caret_analyze/pull/565))
+
+- **Fix**: ignore Agnocast for CI (GitHub Workflow). ([caret #216](https://github.com/tier4/caret/pull/216))
+
+- **Update**: add description to path search example for large ROS 2 application. ([caret_doc #367](https://github.com/tier4/caret_doc/pull/367))
+
+- **Fix**: fix failed to find callback. ([caret_analyze #567](https://github.com/tier4/caret_analyze/pull/567))
+
+- **Test**: fix unable to run pytest in github actions. ([caret_analyze #569](https://github.com/tier4/caret_analyze/pull/569)), ([ros2caret #207](https://github.com/tier4/ros2caret/pull/207))
+
+- **Fix**: correct mypy errors/warnings. ([caret_analyze #570](https://github.com/tier4/caret_analyze/pull/570))
+
+- **Fix**: If the final node of the path is a take implementation, calculate the latency without exception. ([caret_analyze #573](https://github.com/tier4/caret_analyze/pull/573))
+
+- **Fix**: raise exception at executor has no callbacks. ([caret_analyze #571](https://github.com/tier4/caret_analyze/pull/571))
+
 ### v0.6.2 <small>\_ Mar 24, 2025</small> {id = "0.6.2"}
 
 - **Test**: Add test for record directory. ([caret_analyze #552](https://github.com/tier4/caret_analyze/pull/552))

docs/configuration/intra_node_data_path.md

@@ -204,7 +204,6 @@ The architecture object whose sub-objects are renamed is saved to a file as expl
 Using the following Python API to use `use_latest_message` on an architecture object. The examples below follow the previous section.
 
 - You can add a callback to a publisher with `insert_publisher_callback` function in `Architecture` class.
-
   - As arguments, the target node name, publishing topic name and publisher callback name must be specified.
 
 - You can update `context_types` to `use_latest_message` between targeted subscription and publisher with `update_message_context` function in `Architecture` class.
@@ -234,11 +233,9 @@ arch.update_message_context('/pong_node', '/ping', '/pong', 'UNDEFINED')
 Using the following Python API to use `callback_chain` on an architecture object. The examples below follow the previous section.
 
 - You can add a callback to a publisher with `insert_publisher_callback` function in `Architecture` class.
-
   - As arguments, the target node name, publishing topic name and publisher callback name must be specified.
 
 - You can add variable passing with `insert_variable_passing` function in `Architecture` class.
-
   - As arguments, the target node name, write callback name and read callback name must be specified.
 
 - You can update `context_types` to `callback_chain` between targeted subscription and publisher with `update_message_context` function in `Architecture` class.

docs/configuration/practical_example.md

@@ -158,7 +158,6 @@ Define an intra-node data path on the loaded architecture object as section of [
    ```
 
    In the example, `path.verify()` tells you two nodes have undefined relationships of input and output.
-
    - input `/topic2` and output `/topic3` in node `/message_driven_node`
    - input `/topic3` and output `/topic4` in node `/timer_driven_node`
 

docs/design/index.md

@@ -15,18 +15,15 @@ CARET load trace data and convert them to graphs and statistics for users to com
 This chapter describes the design policy and key points as listed below. As the chapter is written for heavy users or developers, most of light users might feel bored.
 
 - Design overview on the architecture and the trace points
-
   1. [Software architecture](./software_architecture/index.md)
   2. [Event and latency definition](./event_and_latency_definitions/index.md)
   3. [Limits and constraints](./limits_and_constraints/index.md)
 
 - Design related to [Recording](../recording/index.md)
-
   1. [Runtime processing](./runtime_processing/index.md)
   2. [Tracepoints](./trace_points/index.md)
 
 - Design related to [Configuration]
-
   1. [Configuration](./configuration/index.md)
 
 - Design related to [Visualization]

docs/recording/recording.md

@@ -12,7 +12,6 @@ Explanation in this page assumes CARET is installed to `~/ros2_caret_ws` and the
 Two terminals are needed for this method; one for executing a target application, another for starting a LTTng session.
 
 1. Open a terminal and launch a target application
-
    - Perform environment settings in the same order as below. CARET's `local_setup.bash` should be applied along with ROS 2's `setup.bash` as the target application refers to CARET/rclcpp
 
      ```sh
@@ -46,7 +45,6 @@ Two terminals are needed for this method; one for executing a target application
      ```
 
 2. Open another terminal and start a LTTng session with the following commands
-
    - Trace data will be stored into the directory whose path is defined as `{ROS_TRACE_DIR}/{SESSION_NAME}`.
      - `ROS_TRACE_DIR` is an environmental variable whose default value is `~/.ros/tracing`  
         (Optional) You can set `ROS_TRACE_DIR` environment variable to change a destination directory where recorded trace data will be stored
@@ -129,7 +127,6 @@ You can start LTTng session using ROS launch system. When you have started a tar
    ```
 
 3. Launch a target application and a LTTng session via the launch file
-
    - Environment settings are still needed, but all operations are performed in just one terminal
 
    ```sh