3.7.0

Development:

• Add renderer jekyllDataProgrammaticString for processing YAML string scalars that do not contain markdown markup and are not intended for typesetting. (istqborg/istqb_product_base#46, #440, #451, sponsored by @istqborg)
• Add option ensureJekyllData for processing standalone YAML files. (#452, #473, sponsored by @istqborg)
• Support user-defined LaTeX environments with LaTeX markup. (#20, #477, suggested by @cdupont)

Fixes:

• Produce more meaningful error message when KPathSea fails to locate a file. (#458, #472, 33e6eef, reported by @Yggdrasil128)
• Fix soft line breaks in citation prenotes and postnotes. (#483, #484, contributed by @lostenderman)

Speed improvements:

• Precompile snippets to improve the speed of setting them. (#467, #479, inspired by the TUG 2024 talk by @josephwright)
• Use an optimized parser to determine Unicode punctuation. (#458, #474, #482, 4c1a7de, co-authored by @Yggdrasil128, sponsored by @istqborg)
  This improves the speed of parsing markdown input by up to 500%.
• Enable option eagerCache by default. (#468, #490, sponsored by @istqborg)
  This improves the speed by up to 25% for large documents with many markdown fragments that require multiple compilation runs.
• Prevent loading the full Markdown package when converting cached markdown fragments. (#487, #491, 40f0803, 6609d43, sponsored by @istqborg)
  This significantly improves the speed for large documents with many markdown fragments that require multiple compilation runs in pdfTeX.

Deprecation:

• Deprecate jekyllDataString renderer and renderer prototype. (istqborg/istqb_product_base#46, #440, #451, sponsored by @istqborg)
  Users should use jekyllDataTypographicString instead.

Continuous Integration:

• Ensure that all code lines are shorter than 72 characters. (#478, e7160d6, 3ac95ef)

Experiments:

• Measure the speed of the Markdown package across recent versions. (249552e, 55ede82, efeaecb, #474, 7b2b243, fcf0064)