docs: update the release notes

docs/strictdoc_01_user_guide.sdoc

@@ -2631,7 +2631,8 @@ This feature is not enabled by default because it has not undergone sufficient t
 [SECTION]
 TITLE: HTML2PDF document generator
 
-[FREETEXT]
+[TEXT]
+STATEMENT: >>>
 StrictDoc offers an experimental feature for converting HTML documents into PDF files. This feature aims to deliver a good PDF printing experience without the necessity of installing more sophisticated printing systems like LaTeX.
 
 There are three methods of PDF printing available:
@@ -2644,8 +2645,9 @@ There are three methods of PDF printing available:
 
 The first two methods require the Chrome browser and chromedriver to be installed on the user's computer.
 StrictDoc downloads chromedriver on demand by default, or uses a pre installed executable if
-``strictdoc export --chromedriver=/path/to/chromedriver`` or the equivalent ``strictdoc.toml`` option
-is given.
+``strictdoc export --chromedriver=/path/to/chromedriver`` or the equivalent ``strictdoc.toml`` option is given.
+
+When printing from the command line (the first method), you can use the ``--generate-bundle-document`` option to have StrictDoc generate a single PDF document that bundles together all individual PDFs.
 
 The third method, the PDF screen, presents a version of the document that is optimized for browser printing. This approach allows for the creation of neatly formatted PDF documents or directly printed documents. Although this method is compatible with any browser, Chrome is recommended for the best printing results. Unlike Firefox and Safari, Chrome maintains the document's internal hyperlinks in the printed PDF.
 
@@ -2661,7 +2663,7 @@ To activate the HTML2PDF screen in the web interface, add/edit the ``strictdoc.t
     ]
 
 This feature is not enabled by default because the implementation has not been completed yet. The underlying JavaScript library is being improved with respect to how the SDoc HTML content is split between pages, in particular the splitting of HTML ``<table>`` tags is being worked out. One feature which is still missing is the ability to generate user-specific front pages with custom meta information.
-[/FREETEXT]
+<<<
 
 [/SECTION]
 

docs/strictdoc_04_release_notes.sdoc

@@ -5,6 +5,30 @@ TITLE: Release Notes
 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>`_.
 [/FREETEXT]
 
+[SECTION]
+TITLE: Unreleased changes
+
+[TEXT]
+STATEMENT: >>>
+This release includes several important improvements. Thanks to @haxtibal for implementing and testing many of the implemented changes.
+
+- Fixed multiple issues related to the handling of the UID field's format and accepted characters, both on its own and when used as part of LINK and ANCHOR tags. [@haxtibal]
+
+- Implemented a more consistent and unified approach to escaping Jinja templates. With this change, the Jinja templates that StrictDoc uses for rendering content are now automatically escaped, except for a few known edge cases that have been handled separately. For more details, see the "HTML Escaping" section of the Design Document, which describes the rationale and approach taken. [@haxtibal]
+
+- Extended the HTML2PDF feature to support the ``--generate-bundle-document`` option, which allows generating a single PDF document from all documents in an SDoc documentation tree.
+
+- Additionally, a project configuration option was added to specify a custom path to the ChromeDriver used by the HTML2PDF printer. [@haxtibal]
+
+- Enhanced the SDoc-ReqIF-SDoc roundtrip to include relation roles such as Refines, Implements, etc. These roles are now recognized in both directions. This feature was requested by a single user and requires further testing.
+
+- Deprecated the passthrough command. All passthrough functionality has been moved to the export command under the option ``--formats=sdoc``. Users are encouraged to switch to the export command, as using passthrough will now trigger a deprecation warning. [@haxtibal]
+
+- Fixed a bug related to editing custom (non-requirement) nodes and adding links between them, based on a report by @elfman2.
+<<<
+
+[/SECTION]
+
 [SECTION]
 TITLE: 0.0.58 (2024-06-25)
 

docs/strictdoc_25_design.sdoc

@@ -138,7 +138,7 @@ One important implementation detail of Arpeggio that influences StrictDoc user e
 [/SECTION]
 
 [SECTION]
-TITLE: HTML Escaping
+TITLE: HTML escaping
 
 [TEXT]
 STATEMENT: >>>

strictdoc/__init__.py

@@ -1,6 +1,6 @@
 from strictdoc.core.environment import SDocRuntimeEnvironment
 
-__version__ = "0.0.59a1"
+__version__ = "0.0.59a2"
 
 
 environment = SDocRuntimeEnvironment(__file__)