Skip to content

Bump version to 0.13.0 #2485

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stanislaw merged 1 commit into from
Sep 28, 2025
Merged

Bump version to 0.13.0 #2485

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified docs/_assets/StrictDoc_Workspace-Roadmap.drawio.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 5 additions & 1 deletion docs/strictdoc_04_release_notes.sdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,14 +47,18 @@ This document maintains a record of all changes to StrictDoc since November 2023

[[SECTION]]
MID: 9e294d6a047b42bf8c55c090fb685b4a
TITLE: Unreleased
TITLE: 0.13.0 (2025-09-28)

[TEXT]
MID: ab6e1c508d224bf1bfb303a808f33f9f
STATEMENT: >>>
This release contains a new feature and several bug fixes.

A new experimental screen, Tree Map, provides visualizations of the overall document tree as well as requirements coverage by source files and tests. The visualization is based on a tree map graph generated using Plotly.js.

StrictDoc now correctly handles Unicode BOM (byte order mark) based on a user report. Previously, SDoc files with a BOM caused parsing errors because the parser did not recognize the marker. Although UTF-8 files normally do not contain BOMs, some tools (likely on Windows) may add them. StrictDoc now strips BOM markers from all input files before parsing, preventing errors if BOMs are present. Thanks to @ichsteffen for reporting this.

In the background, we have started removing the legacy ``Section/[SECTION]`` code. The core still supports the old ``[SECTION]`` syntax, but we are incrementally migrating all unit, integration, and end-to-end tests to the new ``[[SECTION]]`` syntax.
<<<

[[/SECTION]]
Expand Down
2 changes: 1 addition & 1 deletion strictdoc/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
from strictdoc.core.environment import SDocRuntimeEnvironment

__version__ = "0.13.0a1"
__version__ = "0.13.0"


environment = SDocRuntimeEnvironment(__file__)
3 changes: 2 additions & 1 deletion strictdoc/features/tree_map/generator.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -508,7 +508,8 @@ def hover_(row_: Any) -> Any:
description="""\
This graph shows which requirements are covered by at least one test.
A requirement is also considered covered if it has child requirements that are
themselves covered by tests.
themselves covered by tests. A source file is considered a test file if its path
contains "tests/".

<ul>
<li>
Expand Down
Loading